Hi,
On Sun, 2007-07-08 at 17:18 +0200, Ludovic Courtès wrote:
> As for the file name and line number, you can in theory get them
> (provided Guile runs in "debug" mode) using `procedure-source' and
> `source-properties', although the details escape me now.
I actually don't think this is true; pro
Hi Andy,
Andy Wingo <[EMAIL PROTECTED]> writes:
> On Sun, 2007-07-08 at 17:18 +0200, Ludovic Courtès wrote:
>> As for the file name and line number, you can in theory get them
>> (provided Guile runs in "debug" mode) using `procedure-source' and
>> `source-properties', although the details escape
Voter registration started at 23:00 GMT on May 16.
The Editors announced a draft for ratification at 20:00 GMT on July 1.
So here is the rest of the schedule:
1. Voter registration ends: 20:00 GMT on July 15.
2. Voting starts: July 29.
3. Voting ends: August 12.
4. Official results anno
Hi,
Jon Wilson <[EMAIL PROTECTED]> writes:
> guile> (date->string (current-date))
> "Wed Jun 27 16:39:42-0400 2007"
> guile> (date->string (julian-day->date (date->julian-day (current-date
> "Wed Jun 27 12:39:43-0400 2007"
>
> Offset by four hours from one another. Of course, the four hours
Hi Marco,
What does PURIFY-MODULE! actually do? The docstring is just almost
clear enough for me to understand its purpose.
`purify-module!' is a procedure in the (guile) module.
Removes bindings in MODULE which are inherited from the (guile) module.
I think the mechanics of what it does are
Hi,
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? (it does
not appear to be) Is there a good reason why it should not be made
accessible?
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
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-
Ciao,
"Jon Wilson" wrote:
>What does PURIFY-MODULE! actually do? [...] Removes
>bindings in MODULE which are inherited from the (guile)
>module. [...] I think the mechanics of what it does are
>clear enough, but from my understanding of modules, it
>seems essentially useless.
You are right. I hav
