[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] Autoloading optional dependencies

From: Felix
Subject: Re: [Chicken-users] Autoloading optional dependencies
Date: Tue, 14 Sep 2010 08:32:52 +0200 (CEST)

From: Alaric Snell-Pym <address@hidden>
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.

Sorry, I can't stop nagging: first, the constructed "<module>#<identifier>"
name will not work for identifiers that are imported from a different
module and then reexported, second: `global-ref' will be deprecated soon.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]