Particularly on (Arrangement) group export (#828, #836), the generators usually modularize the generated file into library modules that may be used from several top-level roots oder modules. The Oberon language, however, requires the routines, types, variables etc. imported from other modules to be referenced with qualified names, i.e., references to a type TypeA, a variable varB, a constant constC, or a routine subD from some module M are supposed to be written as M.TypeA, M.varB, M.constC, and M.subD(...) from outside the module M, notwithstanding the IMPORT M clause. The Oberon generator fails to insert these qualifications, however.
Particularly on (Arrangement) group export (#828, #836), the generators usually modularize the generated file into library modules that may be used from several top-level roots oder modules. The Oberon language, however, requires the routines, types, variables etc. imported from other modules to be referenced with qualified names, i.e., references to a type
TypeA, a variablevarB, a constantconstC, or a routinesubDfrom some moduleMare supposed to be written asM.TypeA,M.varB,M.constC, andM.subD(...)from outside the moduleM, notwithstanding theIMPORT Mclause. The Oberon generator fails to insert these qualifications, however.