|Project on Compiler firstname.lastname@example.org (1994-01-13)|
|Re: Project on Compiler email@example.com (1994-01-13)|
|Re: Project on Compiler jhall@garden.WPI.EDU (1994-01-13)|
|Re: Project on Compiler firstname.lastname@example.org (1994-01-14)|
|Re: Project on Compiler email@example.com (Kurt Bischoff) (1994-01-14)|
|Re: Project on Compiler firstname.lastname@example.org (1994-01-16)|
|From:||email@example.com (Darin Johnson)|
|Organization:||The Avant-Garde of the Now, Ltd.|
|Date:||Sun, 16 Jan 1994 21:10:53 GMT|
> Second, you will save a good deal by implementing only elementry or
> no error recovery (ie., simply terminate on error). Of course, you'll miss
> an important subject by not doing this, and it may not be admissable to
> your teacher.
But if the students actually have to write sample programs in the
language to compile, they will quickly learn the lesson about how
important error handling is :-)
> As mentioned, the fastest way to do the parser is with a tool and a
> predefined grammar, but a parser for full pascal can be finished in 2
> weeks to 1 month in normal C or Pascal code.
Here, as in other places I suspect, what is done is that you're
given a nearly completed grammar in YACC, and then that must be
modified. Doing one from scratch might be a bit more instructive,
but it takes so much extra time it's probably not worth it.
For instance, a new type or construct must be added to the grammar,
or a the last remaining conflicts must be removed, or error handling
must be added.
Return to the
Search the comp.compilers archives again.