I assume you must be referring to finally blocks in generated C++
parsers, and goto statements in generated C parsers (i.e. not in
the runtime)?

As Sidharth has already pointed out, there are ways around this.
While it may not produce the prettiest code in the world, this is
a concession that I am willing to make for generated code that I
do not have to maintain.  Isn't that the whole point of ANTLR?

Geoff


On Wed, Oct 07, 2009 at 09:18:01AM -0700, Jim Idle wrote:
> I did think about this, but the main issue is that PHP does not support 
> try..catch..finally and the PHP guys refuse to implement goto (which in my 
> opinion is a little over-zealous, despite the fact that any sensible 
> programmer would not use goto except in exceptional circumstances. It means 
> that generating PHP as a target is likely impossible without a lot of 
> convoluted messing around or producing a version of PHP that has a goto in 
> it. If you have to wrap the C runtime in PHP and then generate C and wrap it 
> in PHP then you might as well just call the C version anyway ;-)
> 
> Jim
> 
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]]
> > On Behalf Of Geoff Speicher
> > Sent: Wednesday, October 07, 2009 9:02 AM
> > To: [email protected]
> > Subject: [antlr-dev] PHP module vs. native runtime
> > 
> > I see there is a native runtime for PHP in the works.
> > 
> > Has there ever been any discussion as to whether it would make
> > sense, as an alternative to a native PHP runtime, to wrap the
> > existing C (or C++) ANTLR runtime into a PHP module?  In theory,
> > this should provide a fast PHP target, without the work of having
> > to write and maintain a separate PHP runtime.
> > 
> > This is something that I am interested in doing in the near term
> > unless someone knows of a reason why it wouldn't work.
> > 
> > Geoff
> > 
> > _______________________________________________
> > antlr-dev mailing list
> > [email protected]
> > http://www.antlr.org/mailman/listinfo/antlr-dev
> 
> 
> 
> _______________________________________________
> antlr-dev mailing list
> [email protected]
> http://www.antlr.org/mailman/listinfo/antlr-dev
_______________________________________________
antlr-dev mailing list
[email protected]
http://www.antlr.org/mailman/listinfo/antlr-dev

Reply via email to