[#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: why the lucky stiff <ruby-core@...>
Date: 2005-12-20 04:03:24 UTC
List: ruby-core #6963
Ryan Davis wrote:

> On Dec 18, 2005, at 11:26 PM, why the lucky stiff wrote:
>
>> We are beyond code freeze but Matz has said he will allow patches for
>> serious bugs.  If he's okay with it, it's literally a single byte  
>> patch.
>
>
> I'd support this fully.
>
> I thought it was a 4 byte patch? "--- " at the start of the yaml  
> stream. Am I mistaken?

It's a change of emitter->headless = 0 rather than emitter->headless = 
1.  Not all YAML documents are triggering this bug.  Primarily typed 
headerless streams.  Such as: gem objects.

> I have a small package that I recently recovered from one of my older  
> laptops that takes N ruby tarballs, unpacks them all, configures and  
> builds them all, installs test/unit on all of them (since I was going  
> back to 1.6 and earlier) and then runs a script of your choice  
> against all of them. I still need to dust it off and polish it up,  
> but I was planning on getting it out to the public soon. I know it  
> has helped me with version testing for ZenWeb and RubyInline.

Hooray!  I want this miracle.

Okay, the fix is checked in.  Thanks to Matz for offering another 
preview release and to all of the friends on this list who brought this 
back to my attention when I was remiss.

_why


In This Thread