Re: [Chicken-janitors] #1225: Strange static compilation behaviour

[Chicken Trac]

#1225: Strange static compilation behaviour
-----------------------+--------------------
  Reporter:  kooda     |      Owner:
      Type:  defect    |     Status:  new
  Priority:  minor     |  Milestone:  4.11.0
 Component:  compiler  |    Version:  4.10.x
Resolution:            |   Keywords:
-----------------------+--------------------

Comment (by evhan):

 Using {{{-no-module-registration}}} is the right thing in this situation.

 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.

 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.

--
Ticket URL: <http://bugs.call-cc.org/ticket/1225#comment:3>
CHICKEN Scheme <http://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.