Related articles |
---|
Re: Grammar for optional elements cfc@shell01.TheWorld.com (Chris F Clark) (2007-06-21) |
A Grammar Writing Question lowell@coasttocoastresearch.com (Lowell Thomas) (2007-07-23) |
Re: A Grammar Writing Question cfc@shell01.TheWorld.com (Chris F Clark) (2007-07-26) |
Re: A Grammar Writing Question gah@ugcs.caltech.edu (glen herrmannsfeldt) (2007-07-26) |
Re: A Grammar Writing Question stephenhorne100@aol.com (Steve Horne) (2007-07-27) |
Re: A Grammar Writing Question DrDiettrich1@aol.com (Hans-Peter Diettrich) (2007-07-27) |
Re: A Grammar Writing Question cfc@shell01.TheWorld.com (Chris F Clark) (2007-07-28) |
Re: A Grammar Writing Question schmitz@i3s.unice.fr (Sylvain Schmitz) (2007-07-29) |
A Grammar Writing Question lowell@coasttocoastresearch.com (Lowell Thomas) (2007-08-07) |
From: | glen herrmannsfeldt <gah@ugcs.caltech.edu> |
Newsgroups: | comp.compilers |
Date: | Thu, 26 Jul 2007 21:45:28 -0800 |
Organization: | Compilers Central |
References: | <07-06-053@comp.compilers 07-07-081 07-07-093 |
Keywords: | parse |
Posted-Date: | 27 Jul 2007 09:26:50 EDT |
Chris F Clark wrote:
(snip regarding C++ parsing)
> Worse, I think that some of the devious examples he came up with
> required not only semantic input (i.e. which identifiers were
> declared as what coming into the sequence), but could change which
> identifiers were being declared (as well as what they were being
> declared as).
I am not so sure what features you are considering, but typedef does
complicate the separation of lexing and parsing. Do you have any
examples of the ambiguous cases?
-- glen
Return to the
comp.compilers page.
Search the
comp.compilers archives again.