Re: Substituting local modules with the same name as the GM2 modules

[Michael Riedl]

Benjamin,

I got John's mail as he is having a stand-alone module "Storage.{def|mod}" as separate compilation unit -

not in the sense of a local module you are currently thinking about.

Gruß

Michael

Am 17.11.23 um 01:16 schrieb Benjamin Kowarsch:

Simply get rid of the local modules.

They can easily be copy pasted out into a separate file and made into separate modules. Any entities that are used by the surrounding module can be defined in a definition module and exported. The former hosting module can then import those identifiers back in.

Local modules should never have been part of the language. This was one of those silly fads of the 1970s where everybody and their dog wanted to make everything "orthogonal" even if there was absolutely no reason to do so, even when doing so would come with a long list of disadvantages, even if doing so unnecessarily increased complexity. Just get rid of them.

On Fri, 17 Nov 2023 at 07:46, john o goyo <jog37@riddermarkfarm.ca> wrote:

Greetings, Gaius.

I am trying to build some old code that uses a different version of
Storage.  I have a local version to reflect this and I am using the "-I"
directive.  The compiler picks up my local version for compiling local
modules but it also uses my local version for gm2 modules.

In particular, examining m2/m2pim/Indexing.def pulled in my local
Storage.def and failed.

Hence my query:  Is it even possible to instruct the compiler to use
local modules for local compilation only (or must I rename them)?

Sincerely,
john