From: Michal Suchanek <hramrach@...>
Date: 2009-02-23T22:57:38+09:00
Subject: [ruby-core:22364] Re: 1.8.7 Specifics

2009/2/23 Akinori MUSHA <knu@idaemons.org>:
> At Mon, 23 Feb 2009 19:48:34 +0900,
> Michal Suchanek wrote:
>> Well, this file is quite lengthy and not very readable even for those
>> who look in it.
>>
>> The ordering by class rather than by feature make it look like there
>> are *many* changes.
>>
>> A single change is listed multiple times for each class it affects so
>> it is not clear what it affects nor that it's in fac t a single concept
>> applied to several classes.
>
> I agree that the file has many points to improve, but the section
> listing compatibility issues is not that lengthy at all.
>
> Speaking of which, the ordering changed in 1.9 and you may like it
> better.

Thanks.

Looking forward to working with 1.9 ;-)

>
>> > I think I never missed mentioning the file in any preview or final
>> > release announcement I issued. ��After all, it is your choice to go
>> > with a guidebook or just stay reading nothing...
>> >
>> > Maybe it was not you but a distributor or packager who did not read it
>> > and called attentions of their users, and in that case we'll have to
>> > try harder to call *their* attensions.
>>
>> Note that the GC semantic change which breaks some C extensions (which
>> was pointed out as a response to 1.8.7 preview2 without diagnosing the
>> reason) is not mentioned in the NEWS file. So a distributor who
>> happily packages 1.8.7 then gets a bunch of C extensions that appear
>> to build fine and then segfault at runtime.
>
> I tried really hard to keep the file accurate and up-to-date, but I
> might have forgotten or missed adding some of the changes.
>
> Could you follow up with a mail reference? ��I'll add an entry for
> that.

The mail that states the issue clearly is here:

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/310354

I hope this email with its references is enough to clarify the issue.
I personally do not use non-core C extensions so I have not
experienced the issue myself.

Thanks for your concern

Michal