+1 except for targeting 1.8.7. The Ruby community as a whole is really pushing to get off of 1.8, so the faster IronRuby gets there, the better.
Ryan On Wed, May 12, 2010 at 9:14 AM, Will Green <w...@hotgazpacho.org> wrote: > Vim ;-) > > While it would be nice to have something like the IronPython Tools for > Visual Studio - http://ironpython.net/tools/ - I'd rather see IronRuby > pass more of RubySpec, get more standard libraries, like OpenSSL, > implemented (I know, I know, patches are welcome), and fix some critical > bugs, like the one that prevents upgrading RubyGems via `gem up --system` > (which in turn prevents the easy use of cool libs like Bundler). > > I personally think that 1.8.7 is a better goal than 1.9.1; I've heard some > prominent Ruby community members like Yehuda Katz complain about 1.9.1 on > Twitter. > > -- > Will Green > http://hotgazpacho.org/ > > > On Wed, May 12, 2010 at 10:58 AM, Thomas Gagne <tgga...@gmail.com> wrote: > >> Personally, I'd like to see integration into VS. >> >> What is everyone using to edit their IronRuby code? >> >> _______________________________________________ >> Ironruby-core mailing list >> Ironruby-core@rubyforge.org >> http://rubyforge.org/mailman/listinfo/ironruby-core >> > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core