From: Dan Sugalski <dan@...>
Date: 2002-01-01T00:20:46+09:00
Subject: [ruby-talk:29859] Re: Ruby parsers in Ruby

At 07:41 PM 12/31/2001 +0900, Benoit Cerrina wrote:

> > Hmmm. I suppose we could run the java version of the ruby parser through
> > the java bytecode->parrot bytecode translator. Dunno what that'd look like
> > for speed, though.
> >
> >
> > Dan
>In any case for now the ruby to java bytecode is a little bit of wishfull
>thinking
>what we do right now is interpret the AST in java, like I said we now have a
>port
>to java of the C interpreter but with a little bit more object orientation
>to it (as
>java allows).
>Dan,
>I don't think this would be a good idea since it would loose most of the
>advantages
>of parrot for ruby which is to be a VM built for dynamic languages.  Dynamic
>languages translated in java bytecode usually have performance problems and
>other problems due mostly to java being made for static languages.

Oh, we don't have to use it as an endpoint, just as a starting point.

>PS: I'm happy that you are taking so much interest in ruby Dan, I see parrot
>as the future for ruby for plenty of reason, one of them being that it gives
>ruby program access to a wider install base and a potentially bigger body of
>extensions.

I rather like Ruby--I think it's a nice language. I'd really like some of 
the core Ruby datatypes to get into the core Parrot source and test suite. 
It'll help keep us honest. (We need to get method dispatch done first, though)

					Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
dan@sidhe.org                         have teddy bears and even
                                      teddy bears get drunk