jomes at microsoft.com
Fri Sep 7 15:40:03 EDT 2007
This is an interesting question. I don't know if we've figured out what should be implemented in C# vs. what should be implemented in Ruby.
IronPython generally takes the approach of creating C# versions of the core Python modules that are written in C. Users then have the option of copying the purely Python libraries over from CPython if they desire to do so.
Clearly IronRuby builtins will all need to be written in C#. And also any standard libs that are written in C in MRI, are probably good candidates for writing in C#. Otherwise, it's probably easier to write then in Ruby :)
John Lam might have more guidance...
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Mike Moore
Sent: Wednesday, September 05, 2007 4:32 PM
To: ironruby-core at rubyforge.org
Subject: [Ironruby-core] IronRuby
First Post! (Sorry, had to be done.)
I'm glad to see more and more folks joining the list. I assume we are all excited about IronRuby or we wouldn't be here. :)
As a way of kicking things off, I'm wondering what everyone thinks are the largest pain points in IronRuby right now. Personally, I'd like to start a listing of all the gaps between Ruby and IronRuby, and rank each item that falls outside of the compiler.
I'd also like to get an idea of which libraries are targeted for implementation in C#, as opposed to using the standard Ruby or Rubinious implementations.
What do you guys think?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironruby-core