From: ptkwt@...1.aracnet.com (Phil Tomson) Date: 2001-12-31T02:40:27+09:00 Subject: [ruby-talk:29732] Re: Ruby parsers in Ruby In article , Benoit Cerrina wrote: > >"Phil Tomson" wrote in message >news:qJyX7.1428$Xe4.1226@news.webusenet.com... >> Wouldn't it be cool to have Ruby playing with Parrot before Python or even >> perhaps Perl? That could be a real coup. >> >> Dan Sugalski has suggested that it would be very helpful if we had a Ruby >> parser written in Ruby. It would initially need to spit out Parrot >> bytecode, but eventually we could give him an AST. >> >> Now, it seems to me that we have at least a couple of projects where we >> parse Ruby in Ruby (actually, three that I know of): >> 1) Markus Liedl's Ruby parser - it was announced a while back on >> Rubygarden that it was recently imported into the CVS tree (I think that >> means Ruby's CVS tree). >> 2) JRuby - It must have a frontend parser written in Ruby and then emits >> Java bytecode, right? >Wrong, this wouldn't work well since it would need ruby first and in any >case >we are not yet emitting java bytecode. >It started like a translation of the c ruby interpreter in java and is being >refactored to enable it to emit java bytecode. So it has a java ruby parser >which builds an AST which is intepreted. Sorry, my misunderstanding. So you parse Ruby in Java and emit Java bytecode, of course that makes sense. It still leaves us with two different projects which create a Ruby parser in Ruby (unless there are others I don't know about). Phil