[fpc-devel] [patch] pscanner: differentiate between EOL & Tab characters from general Whitespace

Marco van de Voort marcov at stack.nl
Sun Aug 22 13:35:17 CEST 2010

In our previous episode, Michael Van Canneyt said:

> I cannot accept this patch as it is.
> It breaks the parser, more specifically NextToken.
> The parser ignores whitespace. It should also ignore the new tokens.

> Other than that, I doubt the usefulness of this patch. 
> You are on the wrong track with what you attempt to do.

He wants the source as a kind of DOM model. That is IMHO a valid use, but I
doubt it is unifiable with the current parser.

This is typically one of the reasons why the "one parser to rule them all"
approach is flawed.

More information about the fpc-devel mailing list