Re: [Chicken-hackers] importing modules of not yet loaded extensions

[Christian Kellermann]

* Alan Post alanp...@sunflowerriver.org [101211 18:42]:
 Generally, however, it is a bit annoying that import is an
 all-or-nothing thing, tightly binding sets of libraries together by
 not being able to separate importing from loading.  Your e-mail here
 notwithstanding.

Generally that is exactly what import does: Separating binding from
loading.

___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-hackers

Re: [Chicken-hackers] importing modules of not yet loaded extensions

[Moritz Heidkamp]

Felix fe...@call-with-current-continuation.org writes:
 Being able to import a module without requiring the loading of the 
 libary is necessary to allow cross-compilation. Chicken separates this
 and I consider it a feature. 

Right, Christian pointed this out, too. I wonder though: Are modules
which use `require-extension' cross-compilable then at all? Or does the
compiler somehow prevent the actual loading from taking place,
effectively replacing them by just an `import'? If that is indeed the
case, why not make `import' behave like `require-extension' in the first
place? Or am I missing something obvious?

 Remember the mantra:

   If in doubt, use `require-extension'.

Amen!

Good night for now :-)
Moritz

___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-hackers