IronRuby is still in "alpha". CLR interop is a place we know is still particularly weak. IronPython just released version 2.0, and is considerably more mature. If your goal is to have a fairly polished dynamic language that runs on .NET, then IronPython is probably a better choice. If you like Ruby and don't mind a few hiccups, then your willingness to file problem reports for issues that you find will be of great help to us.
Things are likely to be a bit slow over Christmas, but I'll see if I can get this fixed before the end of the year. -----Original Message----- From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Gabriel Rotar Sent: Monday, December 15, 2008 12:49 PM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] Xna+IronRuby+RubyNewb=headache Dudu Baião wrote: > The IronRuby it's not passing correctly the parameters for the super > class methods. That is a bummer :( Hopeful IronRuby will improve over time. Guess I'll try with IronPython -- Posted via http://www.ruby-forum.com/. _______________________________________________ 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
