Context Navigation

Changes between Initial Version and Version 1 of Ticket #1225, comment 3

initial	v1
1	1	Using {{{-no-module-registration}}} is the right thing in this situation.
2	2
3		The reason for the observed behaviour is as follows: when compiling a file with a module in it, the module information has to go ~~somewhere by default. When {{{-emit-import-library}}} (or {{{-J}}}) is used, that information is put in the generated import file. If the module information isn't~~ emitted, however, it's left within the compiled file itself so that the semantics of the program are preserved.
	3	The reason for the observed behaviour is as follows: when compiling a file with a module in it, the module information has to go ''somewhere'' by default. When {{{-emit-import-library}}} (or {{{-J}}}) is used, that information is put in the generated import file. If the module information ''isn't'' emitted, however, it's left within the compiled file itself so that the semantics of the program are preserved.
4	4
5	5	Obviously in the example above that's not desirable, since it leaves import forms within the compiled code. {{{-no-module-registration}}} is the right way to disable this behaviour.