I agree with you. Until 1.8.7 is the release everyone is using we
should not be targeting it piece-meal. 1.9 mode could satisfy peoples
desire for these features, but for me we need trunk to target the most
common Ruby version and only one version.
-Tom
On Sat, Sep 20, 2008 at 6:53 AM, Marcin Mielżyński <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> Most 1.8.7 features that came from 1.9.1 are to make transition from 1.8 to
> 1.9 series easier. Majority of them is just a copy (with minor changes to
> match 1.8.x api), but there is a lot of tricky examples that behave
> _differently_ under 1.9.x, 1.8.6 and 1.8.7, like:
>
> puts [1,2,3].select.each{|e| p e}
>
> For example, Kernel#p is to blame here since it returns it's argument in 1.9
> but not in 1.8.7, it doesn't make sense to port all the behavior from 1.9.x
> to 1.8.7 since it would end up 1.9.x just without yarv and all the fancy
> syntax features (well, and encoding support of course).
>
> Of course, nobody should ever rely on such temporal 1.8.7 behavior. So, my
> thinking is: since jruby is already trying to support both modes in common
> code base, we don't need 1.8.7 mode at all, 1.9 mode _is_ there with a flick
> of the wrist by just typing --1.9.
>
> Marcin
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
--
Blog: http://www.bloglines.com/blog/ThomasEEnebo
Email: [EMAIL PROTECTED] , [EMAIL PROTECTED]
