[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: |
Mon, 13 Sep 2010 05:03:07 -0400 (EDT) |
From: Alaric Snell-Pym <address@hidden>
Subject: Re: [Chicken-users] Autoloading optional dependencies
Date: Mon, 13 Sep 2010 09:40:06 +0100
> On 09/13/10 07:52, Felix wrote:
>
>> 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.
>
> I've just taken a look at how autoload works. Basically:
>
> (autoload foo bar)
>
> expands into something roughly like:
>
> (define bar (lambda args
> (require foo)
> (let ((tmp (global-ref foo#bar)))
> (set! bar tmp)
> (apply tmp args))))
>
Oh, it already seems to take care of the module prefix.
In that case, everything is fine, then. Sorry for the noise.
cheers,
felix
- [Chicken-users] Autoloading optional dependencies, Alaric Snell-Pym, 2010/09/11
- Re: [Chicken-users] Autoloading optional dependencies, Felix, 2010/09/14
- Re: [Chicken-users] Autoloading optional dependencies, Alex Shinn, 2010/09/14
- Re: [Chicken-users] Autoloading optional dependencies, Felix, 2010/09/14
- Re: [Chicken-users] Autoloading optional dependencies, Alex Shinn, 2010/09/14
- Re: [Chicken-users] Autoloading optional dependencies, Felix, 2010/09/15