<?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: Specifying Options in Rails</title>
	<atom:link href="http://www.flyingmachinestudios.com/2008/03/08/specifying-options-in-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.flyingmachinestudios.com/2008/03/08/specifying-options-in-rails/</link>
	<description></description>
	<pubDate>Sat, 22 Nov 2008 02:19:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Daniel Higginbotham</title>
		<link>http://www.flyingmachinestudios.com/2008/03/08/specifying-options-in-rails/#comment-4</link>
		<dc:creator>Daniel Higginbotham</dc:creator>
		<pubDate>Tue, 25 Mar 2008 20:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.flyingmachinestudios.com/?p=1#comment-4</guid>
		<description>On the other hand, it might be confusing to have a new &lt;code&gt;Options&lt;/code&gt; class because perceptive people like yourself will look at it and think the same thing you did, and wonder what the point is.  In either case, I've found that using something a non-primitive object like this is useful when you're building up options over multiple methods.

Doing so helps keep things DRY, reduces failure distance, and communicates more explicitly.</description>
		<content:encoded><![CDATA[<p>On the other hand, it might be confusing to have a new <code>Options</code> class because perceptive people like yourself will look at it and think the same thing you did, and wonder what the point is.  In either case, I&#8217;ve found that using something a non-primitive object like this is useful when you&#8217;re building up options over multiple methods.</p>
<p>Doing so helps keep things DRY, reduces failure distance, and communicates more explicitly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Higginbotham</title>
		<link>http://www.flyingmachinestudios.com/2008/03/08/specifying-options-in-rails/#comment-3</link>
		<dc:creator>Daniel Higginbotham</dc:creator>
		<pubDate>Tue, 25 Mar 2008 20:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.flyingmachinestudios.com/?p=1#comment-3</guid>
		<description>That does look very much like a Struct :) I started out with something different, and in changing it I didn't realize the similarity.

One of the useful parts of my code is the &lt;code&gt;conditions&lt;/code&gt; method in ActiveRecordOptions , which then gets called by &lt;code&gt;to_hash&lt;/code&gt;. Can Structs do this or something similar by default? That would be helpful.

Using the Options class might still be a better choice because its purpose is more explicit. So perhaps it is a reinvention, but so far I find it a useful reinvention :)</description>
		<content:encoded><![CDATA[<p>That does look very much like a Struct :) I started out with something different, and in changing it I didn&#8217;t realize the similarity.</p>
<p>One of the useful parts of my code is the <code>conditions</code> method in ActiveRecordOptions , which then gets called by <code>to_hash</code>. Can Structs do this or something similar by default? That would be helpful.</p>
<p>Using the Options class might still be a better choice because its purpose is more explicit. So perhaps it is a reinvention, but so far I find it a useful reinvention :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Weber</title>
		<link>http://www.flyingmachinestudios.com/2008/03/08/specifying-options-in-rails/#comment-2</link>
		<dc:creator>Greg Weber</dc:creator>
		<pubDate>Tue, 25 Mar 2008 20:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.flyingmachinestudios.com/?p=1#comment-2</guid>
		<description>seems like you are reinventing the Struct, (but adding to_hash).</description>
		<content:encoded><![CDATA[<p>seems like you are reinventing the Struct, (but adding to_hash).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
