| Related articles |
|---|
| Handling the typedef problem with a modifiable grammar bburshte@pyrps5.eng.pyramid.com (1992-01-09) |
| Programming language syntax design (was Re: ... typedef problem) landauer@morocco.Eng.Sun.COM (1992-01-14) |
| Programming language syntax design (was Re: ... typedef problem) bevan@computer-science.manchester.ac.uk (Stephen J Bevan) (1992-01-15) |
| Re: Programming language syntax design (was Re: ... typedef problem) anw@maths.nott.ac.uk (1992-01-17) |
| Re: Programming language syntax design (was Re: ... typedef problem) bliss@sp64.csrd.uiuc.edu (1992-01-20) |
| Newsgroups: | comp.compilers |
| From: | bliss@sp64.csrd.uiuc.edu (Brian Bliss) |
| Keywords: | syntax, parse, design |
| Organization: | UIUC Center for Supercomputing Research and Development |
| References: | 92-01-043 92-01-071 |
| Date: | Mon, 20 Jan 92 21:04:32 GMT |
I don't want to start up the thread on the typedef problem all over again,
but as far as it is concerned with language design...
Consider the production for a C declaration statement, ala K&RII:
declaration -> dec_specifiers init_dec_list
^ by requiring a colon (like pascal) or some
other token right there, the entire problem
could have been avoided.
bb
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.