In message 0873F763.20010309182845.FOO-3141.frank@g-n-u.de Frank Heckenbach writes:
[snip]
The strict for keeping legacy apps running, the loose mode for interoperability.
I don't see how this should solve Dave's problem. AFAIUH, he's using "all" of GPC's features (i.e., not restricted to a particular standard or dialect) and was only disturbed by a particular keyword.
That's correct. This particular code started off in UCSD Pascal, was then migrated to Edinburgh Portable Compilers Extended Pascal (which complied with a subset of the *draft* Extended Pascal Standard, I think), and then migrated to GPC. In the migration to GPC (in late 1999) I found some Extended Pascal features we were using did not work reliably enough, and had to replace then by (probably) Borland/UCSD features. So it's a mismash ...
[snip]
As I already said in other mails, I'd prefer some more options to fine-tune the dialect (like --disable-keywords), so one doesn't have to use a dialect option just because of one single issue (like in this case). (Besides, those options are probably quite a bit easier to implement than new dialect versions because they only affect specific parts of the compiler.)
As a user, that's my preference too.