Hi,
Jon Wilson <[EMAIL PROTECTED]> writes:
> Ludovic Courtès wrote:
>> And no, it's not documented (patch welcome! ;-)).
>>
> Here we are: (attached)
Thanks! I applied it.
Ludovic.
___
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.
Hi Ludovic,
Thanks for the suggestion. I likely never would have found
save-module-excursion on my own.
Ludovic Courtès wrote:
And no, it's not documented (patch welcome! ;-)).
Here we are: (attached)
Regards,
Jon
Index: api-modules.texi
=
Hi Jon,
Jon Wilson <[EMAIL PROTECTED]> writes:
> Thanks for the swift reply. However, I meant to ask whether or not
> the fluid "the_module" is accessible from scheme as a fluid.
Ah sorry. Then the answer is "no".
Then indeed, you have to go through `dynamic-wind'. Arguably, this is
not very
Hi Ludovic,
Thanks for the swift reply. However, I meant to ask whether or not the
fluid "the_module" is accessible from scheme as a fluid. We can easily see:
guile> (fluid? (current-module))
#f
So the value returned by (current-module) is not a fluid, and thus my
shortened version of load-
Hi,
Jon Wilson <[EMAIL PROTECTED]> writes:
> I was poking around the source (guile-core/libguile/modules.c), and
> noticed that the current toplevel module is stored in a fluid named
> (in C, anyway) "the_module". Is this fluid accessible from scheme?
Yes, using `(current-module)'.
Thanks,
Ludo
