[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Thread and guile environment
From: |
Linas Vepstas |
Subject: |
Re: Thread and guile environment |
Date: |
Mon, 12 Jul 2010 15:24:16 -0500 |
Hi,
On 10 July 2010 03:22, Andy Wingo <address@hidden> wrote:
> Hi,
>
> On Fri 09 Jul 2010 22:23, Neil Jerram <address@hidden> writes:
>
>> Andy Wingo <address@hidden> writes:
>>
>>> Interestingly, the first thread has you in (guile-user), but the second
>>> has you in (guile). So you don't see the full definition of format, nor
>>> do you see hug.
>>
>> That's what I thought too. But in that case I have no idea why my
>> '(define-module (guile-user))' suggestion didn't work.
>
> I think bug.scm was loaded in the main module -- the threads just tried
> to call a function defined by bug.scm, and as they were in (guile), not
> (guile-user), there was the error
Yes, this sounds a lot like the bug I saw few years ago ...
.
>>> But it's quite ugly. Does anyone have any input as to what module should
>>> be current when a thread previously unknown to Guile enters Guile?
>>
>> Surely it has to be (guile-user), since that what the end of boot-9.scm
>> moves into - and hence is well-established for the single thread case.
>
> Agreed. I just pushed the following patch, which fixes Cedric's case.
Thanks.
Is this for guile1.8.8 or for 2.0?
--linas
Re: Thread and guile environment, Cedric Cellier, 2010/07/12