On Mon, 20 Nov 2006, Daniel Berger wrote:

> Hugh Sasse wrote:
> > On Mon, 20 Nov 2006, Eric Hodel wrote:
        [...]
> > > Not backwards compatible.
> > > 
> > > $ ruby -e 'p %w[1.8.1 1.8.2 1.8.9 1.8.10].sort'
> > > ["1.8.1", "1.8.10", "1.8.2", "1.8.9"]
> > >     
> > 
> > That's why I was proposing that the feature be backported to 1.6 etc.
> >         Hugh
        [...]
> So, let me get this straight people.  We're avoiding 1.8.10 because of the way
> it *sorts*?  Not backwards compatible....with what?

Earlier versions of ruby that rely on this behaviour.  But now see
Ruby-Talk:09590, which kills this thread.  I can't see a way around
that implementation, unless possibley we make RUBY_VERSION_CODE a
floating point constant so we can wedge more decimals in between 1.8.8
and 1.8.9 etc.  
> 
> - Dan
> 
> PS - No version strings either.  Just ask the Perl community how well those
> have gone over.

That's why I wanted a full class.  Even then it's tricky.
> 
        Hugh.