On Sat, May 24, 2008 at 11:24 AM, Peter Bex <[EMAIL PROTECTED]> wrote: > > Another question: what will happen to use, require, require-extension, > require-for-syntax and the (declare ...) language? > This is a nice time to clean up some stuff (for example, removing the > various confusing require-* forms)
It's true that all these forms are confusing. The situation will become simpler when using modules, as compile-time code is loaded automatically (when using import libraries). "require-for-syntax" will not be necessary, I could imagine. "require" is just a load-once and doesn't hurt. "require-extension" is still required (so to speak), since it is the official way of loading extensions, and the module system does explicitly not address the difference between loading (require-extension) and linking (declare (uses ...)) to allow static linking (i.e. import doesn't mean: load code - it just makes module bindings available. Throwing these together makes static linking and cross-compilation harder). "use" is just a shortcut for "require-extension", just like "add1" is a shortcut. cheers, felix _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
