On Mon 09 Nov 2015 08:51, taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:
>> I do not understand what you mean by "degenerate" modules :) An >> interpreted module should act the same as a compiled module. I am >> interested to hear what difference you can perceive between the two. > > The relevant bug report is <http://bugs.gnu.org/15602>. > > According to Ludo's explanation, compiling a module file leads to the > module being created in the runtime, but with syntax bindings only, and > runtime bindings missing. That's what I mean with "degenerate" module > for lack of a better term. Loading the same file explicitly afterwards > (or using load-compiled on the generated .go) seems to solve the issue. Ah, I see. Well, one workaround for this issue, if you wanted to work around it, would be to load the file before compiling it. In that way the module would already be loaded at the right phase. This wouldn't cost very much AFAIU. Andy
