[Oberon] Module aliases - what is the correct way to handle them
fusionfile at gmail.com
Tue Jul 14 22:35:42 CEST 2020
On 2020-07-14 09:24, Jörg wrote:
> Now back to topic A): the Oberon report states „If the form "M := M1" is used in the import list, an exported object x declared within M1 is referenced in the importing module as M.x
> This definition does not specify, whether IMPORT M := M1, N := M1; is allowed.
> Looking at other Oberon constructs like
> S = “This is a funny string“;
> S1 = S;
> S2 = S;
> I1 = INTEGER;
> I2 = INTEGER;
> I don‘t see a reason why import aliases should forbid multiple imports.
I think I'm now convinced that it makes sense to allow repeated imports
of the same module with different qualifiers. Does anyone see any
potential problems with it?
More information about the Oberon