From: Christophe Broult Date: 2001-04-02T21:20:55+09:00 Subject: [ruby-talk:13436] Re: Using Antlr for Ruby? (was RE: Re: why won't "( a) = 1" parse?) This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0BB6F.8476B530 Content-Type: text/plain; charset="ISO-8859-1" > -----Original Message----- > From: Leon Brocard [mailto:acme@astray.com] > Sent: Monday, April 02, 2001 8:17 AM > To: ruby-talk@ruby-lang.org > Subject: [ruby-talk:13435] Re: Using Antlr for Ruby? (was RE: Re: why > won't "( a) = 1" parse?) > > > Christophe Broult sent the following bits through the ether: > > > I was also thinking that it would be nice to use Antlr to > generate parsers > > in Ruby and after that being able to kind of "bootstrap" > Ruby with Ruby. > > FWIW I spent a couple of days attempting to get Antlr to generate > parsers in Perl. I gave up as I didn't even have the lexer working by > then. Feel free to try, though ;-) I cannot work on that in the near future but I will keep the idea in the back of my mind:-( Christophe ------_=_NextPart_001_01C0BB6F.8476B530 Content-Type: text/html; charset="ISO-8859-1" RE: [ruby-talk:13435] Re: Using Antlr for Ruby? (was RE: Re: why won't "( a) = 1" parse?)

> -----Original Message-----
> From: Leon Brocard [mailto:acme@astray.com]
> Sent: Monday, April 02, 2001 8:17 AM
> To: ruby-talk@ruby-lang.org
> Subject: [ruby-talk:13435] Re: Using Antlr for Ruby? (was RE: Re: why
> won't "( a) = 1" parse?)
>
>
> Christophe Broult sent the following bits through the ether:
>
> > I was also thinking that it would be nice to use Antlr to
> generate parsers
> > in Ruby and after that being able to kind of "bootstrap"
> Ruby with Ruby.
>
> FWIW I spent a couple of days attempting to get Antlr to generate
> parsers in Perl. I gave up as I didn't even have the lexer working by
> then. Feel free to try, though ;-)

I cannot work on that in the near future but I will keep the idea in the back of my mind:-(

Christophe

------_=_NextPart_001_01C0BB6F.8476B530--