On Sat, Jun 28, 2014 at 05:39:35PM +0200, Felix Winkelmann wrote: > > > > I'm not convinced we need separate loading and importing either, as long > > as it doesn't interfere with separate compilation. Right now everyone > > always ends up doing (use ...) anyway. Perhaps Felix can show us an > > example where only an import (no loading of code) is useful, or otherwise > > how I'm missing the point? > > Static linking? Having several modules (library units) in a single > library (as in libchicken itself)?
As far as I understand, if you statically link a program which contains a (use foo) clause, you can link it together with foo.a, and it won't try to load anything dynamically. Is that correct? If it's correct, I don't see why (require-library) and (import) must be separate things from (use). They could all perform the same operation (ie, importing the module identifier and loading the code if it isn't loaded yet). Cheers, Peter -- http://www.more-magic.net _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
