On 6/14/06, Nicolas Cannasse <[EMAIL PROTECTED]> wrote:
> Hi Robert,
>
> Your project of a Ruby compiler targetting Neko sounds great. I don't
> think I can offer any reliable and/or valuable help for this summer,
> but I'd certainly like to hear more about that. In particular, I'm
> wondering if you've defined (more or less formally) anywhere a
> specification of the subset of Ruby which you handle (or plan to
> handle), and which features of Ruby wouldn't fit into the VM. I
> personnally believe that these "dynamic" languages like Python or Ruby
> have too many not-so-useful features which make them unsuitable for a
> decent compilation, I'd like to see that pointed out.
>
> Cheers.
I think everything is possible, but this is just a question of performance.
I agree with Nicolas. The plan is to do as little as possible in Neko
code and as much as possible in pure-Ruby code (when it comes to
Ruby's std lib classes). As an example, when implementing Ruby's Array
class only a minimal subset of methods should be written in Neko while
the rest use this subset but are written in pure Ruby.
Regards,
Robert
--
Neko : One VM to run them all
(http://nekovm.org)
