[#6864] ruby 1.8.4 rc breaks alias_method/rails in bad ways — "Ara.T.Howard" <ara.t.howard@...>

20 messages 2005/12/09
[#6870] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...> 2005/12/12

Ara.T.Howard wrote:

[#6872] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, [ISO-8859-15] Florian Growrote:

[#6873] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — James Edward Gray II <james@...> 2005/12/12

On Dec 12, 2005, at 1:19 PM, ara.t.howard@noaa.gov wrote:

[#6874] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, James Edward Gray II wrote:

[#6891] Time.utc! and Time.localtime! — Daniel Hobe <hobe@...>

Writing a script yesterday I found out, much to my surprise, that the

16 messages 2005/12/14

[#6918] change to yaml in 1.8.4 — ara.t.howard@...

14 messages 2005/12/16

[#6934] 1.8.x, YAML, and release management — Ryan Davis <ryand-ruby@...>

I'm concerned that 1.8.3's acceptance of non-backwards-compatible

28 messages 2005/12/18

[#6996] Problems building 1.8.4 with VS8 C++ Express Edition (cl 14.00) — Austin Ziegler <halostatue@...>

Visual Studio C++ 2005 Express Edition (VS 8.0)

20 messages 2005/12/27

Re: 1.8.x, YAML, and release management

From: URABE Shyouhei <shyouhei@...>
Date: 2005-12-19 12:43:26 UTC
List: ruby-core #6953
Hi.

Hugh Sasse wrote:

>Where is this constraint set?
>

In matz himself.  He announced that in, for instance, [ruby-dev:9366].

>Modifying the code that handles
>version numbers to support larger minor versions would seem to be
>useful.
>

That's true.  I agree.

Sad thing is that requires a reconstruction of very low-level C 
infrastructure in ruby source code.  You can grep *.c files with 
RUBY_VERSION_CODE to see how ruby itself implies its version number 
being three-digit decimal numbers.  As 1.8 is a stable branch, I don't 
think it's a good idea to touch such a fundamental point.

>It would also help integration of gem version number
>handling within ruby.
>

So what? That's another story.

>Such a change should not break existing
>assumptions,
>

Yes it does.  You can see how string comparisons are used in ruby 
version checking in:

http://raa.ruby-lang.org/gonzui/search?q=RUBY_VERSION&fm=all

It's almost an idiom.

>since they seem to be based on single digit version
>numbers (or at leeast that's true since about 1.4.4 when I joined
>the community).  Therefore, in the context of this debate, it should
>be possible to make such a change in 1.8.[45].
>
>       Hugh 
>  
>

In This Thread