| Since compilers are one of the areas where everyone agrees that FPLs
| are the right tool for the job, there should be a standard pattern to
| deal with include files. Am I missing something essential?

No.  Parsec is an excellent library, but I think there's a 
design flaw in that you can't write your own lexer.  The 
"traditional" thing to do is write a lexer, which can deal 
with include files, etc, as you want.  Parsec would then 
be presented with a list of tokens, rather than a list of
chars as at present.  Doing this would also avoid the hassle
of having to remember to skip whitespace here, there and
everywhere, which cluttered up a parser I wrote recently 
with parsec.

Daan, what do you say?

Other than that, Parsec is really good.  I particularly liked
the error reporting stuff.

J

Reply via email to