Related articles |
---|
LL Parser problem jdlessl@yahoo.com (2004-08-09) |
Re: LL Parser problem jdlessl@yahoo.com (2004-08-10) |
Re: LL Parser problem wyrmwif@tsoft.org (SM Ryan) (2004-08-11) |
Re: LL Parser problem nick.roberts@acm.org (Nick Roberts) (2004-08-13) |
Re: LL Parser problem cfc@shell01.TheWorld.com (Chris F Clark) (2004-08-15) |
Re: LL Parser problem nick.roberts@acm.org (Nick Roberts) (2004-08-23) |
Re: LL Parser problem rich@pennware.com (Richard Pennington) (2004-08-25) |
Re: LL Parser problem vbdis@aol.com (2004-09-03) |
[1 later articles] |
From: | jdlessl@yahoo.com (Jared Lessl) |
Newsgroups: | comp.compilers |
Date: | 10 Aug 2004 17:35:42 -0400 |
Organization: | http://groups.google.com |
References: | 04-08-036 |
Keywords: | parse |
Posted-Date: | 10 Aug 2004 17:35:42 EDT |
> [Special case the lexer to return a mutant < token after an array
> name. -John]
Except that in AREV, any variable or function return value can be an
array of this type. The only assurance I can have that a '<' is not
an array index is if it immediately follows a literal or numerical
value.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.