--0016363b7e9c80b0a70462ce37f2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Fri, Feb 13, 2009 at 4:50 AM, James Coglan <jcoglan / googlemail.com>wrote:

>
> This begs the question of whether 1.9 should guarantee insertion order for
> hashes. Since hashes are not inherently ordered beings, wouldn't it make
> more sense to provide an OrderedHash subclass that explicitly provides that
> behaviour? At least then it would be clearer if you were using a 1.9
> feature
> that won't work on 1.8.


For Ruby 1.9, the issue is settled.  Ruby 1.9 is a new and different Ruby
than Ruby 1.8.6.

To make an analogy from ancient history, there is a Rubicon between Ruby
1.8.6 and Ruby 1.9.  Because of the consequences of crossing the Rubicon,
one should make a conscious decision to do so.

Ruby 1.8.7 represents the middle of the river.

-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale

--0016363b7e9c80b0a70462ce37f2--