Re: Predefined Pragma Variables

[Brian Hawley <brian.hawley@bigfoot.com>]

Hi there.

Michael van Acken <mvacken@t-online.de>:
> Any comments (additional variables, different names or definitions)?

Tim Teulings <tim@edge.ping.de>:
>One more variable/pragma (f.e. COMPILER = "ooc"), that identifies ooc
>itself. This would make it easier to compile code which is not only for
>ooc but for other compilers (f.e. vthe various OberonSystem compilers).
>One could f.e. choose different includes for different compilers.

This is a good idea, and should be done, but almost moot for the moment
because almost(?) all other Oberon compilers don't yet support any pragmas
at all. Still, this might change.

Given that this might change, we should add a LANGUAGE pragma that would
initially be defined as "Oberon-2" with OOC. Other compilers could define
it as "Oberon" (no (or partial) O2 extensions, like Edipar), "Active Oberon"
(Native S3), or "Component Pascal" (BlackBox). OOC could eventually support
these as well, perhaps by setting LANGUAGE at the beginning or with modular
compiler front ends.

Brian Hawley