🚀 go-pugleaf

> [ from Gernot Heiser, regarding the DEC compiler: ]
>    - identifiers imported in the definition module are not known in the
>      implementation module, they must be imported again. This will generate
>a
>      compile-time error in most other Modula-2 systems
> [ and in another letter as explanation: ]
>Imports ARE declarations! PIM2 ed2 p 143 (sorry, I don't have ed3 at hand, but
>there should be no difference concerning this point):
>"Every identifier occuring in a program must be introduced by a declaration,
>unless it is a standard identifier."
>This means, importing an identifier into a definition module declares this
>identifier, and hence makes it "available in the corresponding implementation
>module without explicit import." (PIM ed2 p 164)

Iff imports are declarations, the above assumption will be right. But
I can't find where this is defined. An import is a way to extend
the scope of a declaration, and therefore makes the declared identifier
visible in the importing module. But it don't move the location of
the declaration.

Both the TDI compiler for Atari-ST and our compiler on IBM/CMS
share my opinion. This isn't very astonishing because they have
the same grandfather: the ETH Zurich 4-pass compiler. And because
our CMS compiler is very similar to the Cambridge system which
runs on several 68K Unix boxes here, I have severe doubts that
the Cambridge compiler will show a different behaviour (which was implied
by your comparsion of the DEC and the Cambridge compiler).

  Thomas

Technical University Berlin               BITNET: HABERNOL@DB0TUI11