Ironruby core - Sep 2007 - 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?

~Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/ironruby-core/attachments/20070905/4d065936/attachment.html

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?

~Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/ironruby-core/attachments/20070907/09463367/attachment-0001.html

Well, from the perspective of a Rubyist, why not write some Ruby 
functions (shims approach) to output C# code automatically as John did 
with RubyCLR?

Josh Nursing

John Messerly wrote:
>
> 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?
>