Saw this earlier today, might be something to think about in the near
future for IronRuby and compatibility.
http://blog.segment7.net/articles/2010/04/23/ruby-1-8-6-policy
-Zac
Looks like we’ll need an IronRuby 1.0.1 that brings us up to 1.8.7.
Unless
we can get to 1.9 faster…
–
Will G.
http://hotgazpacho.org/
Yup, thats what it appears. I’m willing to work on either, just depends
on what people’s needs are. I personally would be prefer just pushing
forward with 1.9 support but I don’t know the state of 1.9 vs 1.8.7
support.
-Zac
Are there any particular 1.8.7 features you know that don’t work in
IronRuby 1.0? Note that you can pass -1.8.7 command line argument to
ir.exe, which enabels some 1.8.7 features.
Tomas
To be honest, no. I went straight from 1.8.6 to 1.9. I never actually
tried to use 1.8.7 so I’m not aware of its differences from 1.8.6 and
1.9.
-Zac
I don’t know how complete we are in respect to 1.8.7, but I don’t think
we should focus on it unless there is considerable requests for it.
Between this Rubygems announcement and Rails, I would expect we’ll start
seeing a stronger move to 1.9 in the next year.
JD