Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [3 earlier articles] |
| Re: Error reporting in LR parsers heirich@cs.ucsd.edu (1989-08-08) |
| Re: Error reporting in LR parsers heirich@cs.ucsd.edu (1989-08-08) |
| Re: Error reporting in LR parsers rusty@garnet.Berkeley.EDU (1989-08-10) |
| Re: Error reporting in LR parsers djones@megatest.com (1989-08-10) |
| Re: Error reporting in LR parsers djones@megatest.com (1989-08-10) |
| Re: Error reporting in LR parsers djones@megatest.com (1989-08-10) |
| Re: Error reporting in LR parsers markg@well.sf.ca.us (1989-08-15) |
| Re: Error reporting in LR parsers eachus@mbunix.mitre.org (1989-08-14) |
| From: | markg@well.sf.ca.us (Mark Grand) |
| Newsgroups: | comp.compilers |
| In-Reply-To: | <1989Aug8.130702.957@esegue.uucp> |
| Organization: | Whole Earth 'Lectronic Link, Sausalito, CA |
Generating a list of acceptable tokens before allowing YACC to perform a
default reduction is expensive. A cheaper way (assumimg a fast
implementation of memcpy) is to take a snapshot of YACC's state stack every
time it gets a new token. That way you can generate a list of the expected
tokens from the snapshot and only have to do it when actually needed.
--
Mark Grand markg@well.sf.ca.usa
GeoMaker Software {apple,pacbell,hplabs,ucbvax}!well!markg
P.O. Box 273124 415-680-1964
Concord CA 94527-3124
Return to the
comp.compilers page.
Search the
comp.compilers archives again.