Am 29.04.2011 00:02, schrieb Joerg Schuelke:
Am Thu, 28 Apr 2011 23:39:35 +0200
schrieb Hans-Peter Diettrich<drdiettri...@aol.com>:

The bug resides in the dirty Delphi OPL definition.

Is it a bug or unspecified behavior? I think it is implemented in the
hope it works good enough.

If you consume a<modifier>  token as<modifier>  or<identifier>  in
respect of the right context of one token, you get rid of this strange
behavior and you will get a real superset of the former language.

So, why not doing it?

The FPC scanner is simply not designed for a look ahead > 1. Especially macro and include file expansion as well as generics require probably a major rewrite of the scanner.
_______________________________________________
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply via email to