<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Wirble in Ruby 1.9</title>
	<atom:link href="http://ruby.tie-rack.org/40/wirble-in-ruby-19/feed/" rel="self" type="application/rss+xml" />
	<link>http://ruby.tie-rack.org/40/wirble-in-ruby-19/</link>
	<description>Ruby.send(:stop, 'messing around')</description>
	<pubDate>Fri, 10 Sep 2010 00:27:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Fred</title>
		<link>http://ruby.tie-rack.org/40/wirble-in-ruby-19/#comment-441</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Tue, 04 Mar 2008 20:32:11 +0000</pubDate>
		<guid isPermaLink="false">http://ruby.tie-rack.org/40/wirble-in-ruby-19/#comment-441</guid>
		<description>It is not recommended to use wirble on your irb if you have large ouptut print out
such as:

Item.find(:all)
which might return 1,000 results 

the ruby process memory will go up to the roof (1.GB ram usage)</description>
		<content:encoded><![CDATA[<p>It is not recommended to use wirble on your irb if you have large ouptut print out<br />
such as:</p>
<p>Item.find(:all)<br />
which might return 1,000 results </p>
<p>the ruby process memory will go up to the roof (1.GB ram usage)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Grigsby</title>
		<link>http://ruby.tie-rack.org/40/wirble-in-ruby-19/#comment-395</link>
		<dc:creator>Dan Grigsby</dc:creator>
		<pubDate>Wed, 02 Jan 2008 18:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://ruby.tie-rack.org/40/wirble-in-ruby-19/#comment-395</guid>
		<description>Thanks.  Very helpful.  IRB w/o the Wirble-ized tab-complete is painful.
</description>
		<content:encoded><![CDATA[<p>Thanks.  Very helpful.  IRB w/o the Wirble-ized tab-complete is painful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
