[fpc-devel] OO rewrite - globals

Hans-Peter Diettrich DrDiettrich1 at aol.com
Mon Jul 26 12:32:23 CEST 2010

Florian Klaempfl schrieb:

>> When a parser is designed to work with exactly one scanner, why should
>> it not inherit from it? 
> Well, with the same argument one could stuff all code in one source file
> and don't separate anything in units.

Encapsulation requires some separation.

> Having parser and scanner separated might also enable more fine grained
> multi threading later one: the scanner creates fills a token queue which
> is read by the parser later on, I know this won't be easy because FPC's
> scanner is parser context sensitive.

At least the scanner "context" is used in many places in other code. A 
hypothetical token stream had to include the full scanner context, i.e. 
file/offset/line/column information, as well as current_settings, for 
*every single* token. Not very practical :-(

> I simply don't like the idea of having one big parser class blob spread
> over multiple include files.

I don't like it as well :-(

That's why I want to remove the semantics code from the parser, later, 
and merge the remaining contents of the include files into an 
<language>.pas parser file.


More information about the fpc-devel mailing list