From: Alaric Snell-Pym <ala...@snell-pym.org.uk> Subject: Re: [Chicken-users] Autoloading optional dependencies Date: Sun, 12 Sep 2010 21:11:45 +0100
> On 09/12/10 15:49, Felix wrote: > >> But that wouldn't work inside modules, because you would have to >> have access to the import library, right? > > If there's macros involved, yes - but then autoloading macros makes no > sense as they're loaded at compile time anyway. When you set up an > autoload, no compile-time loading happens (no import library, etc) so > the macros from the library aren't loaded - but at run time, if you > call > a procedure imported from the library, then the library is > run-time-loaded. When the toplevel variable passed to `autoload' refers to a module binding, then you have to import it, otherwise it refers to an undecorated toplevel variable. cheers, felix _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users