From: ptkwt@...1.aracnet.com (Phil Tomson)
Date: 2002-01-01T03:43:03+09:00
Subject: [ruby-talk:29881] Re: Ruby parsers in Ruby

In article <5.1.0.14.2.20011231101727.02243eb8@pop.sidhe.org>,
Dan Sugalski  <dan@sidhe.org> wrote:
>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.

I don't think we need to do that.  Hopefully we can get either the 
ruby-parser in the 1.7 CVS going, or perhaps (and I kind of prefer this) 
build on the ruby parser example that comes with Rockit.  Rockit seems 
like a more advanced parser builder than the other options.

>> >
>> >
>> > 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.
>

I think we might be wasting effort trying to go down that road.  Effort 
that would be better spent working on a true RubyinRuby solution which can 
be used by several other projects as well.

Phil