[.]
-
[up]
[top] -
indexREADMEmakescriptsconfigure
These are all fairly simple examples, but they give a good
impression of what you can do.
The idea is that each scanner or parser is
an independent class derived from iter.
So scanners and parser are interchangeable,
which means that you can employ
a (yacc) parser as a scanner.
I have, unfortunately, no example of this,
but it seems a nice idea. Right?
Somehow, the simple examples do not allow
for proper error messages.
When the generation of y.error.c, which is usually appended
to the yacc output, gives problem, make YERROR false.
