Re: bug: defining things in different threads

2008-11-21 Thread Linas Vepstas
The saga continues... 2008/11/20 Linas Vepstas <[EMAIL PROTECTED]>: > 2008/11/15 Neil Jerram <[EMAIL PROTECTED]>: >> 2008/11/12 Linas Vepstas <[EMAIL PROTECTED]>: >> >>> Yes, of course, the problem remains. >> >> Explanation: >> >> Thread 1 is the first thread that does any Guile stuff, so it load

Re: bug: defining things in different threads

2008-11-20 Thread Linas Vepstas
2008/11/15 Neil Jerram <[EMAIL PROTECTED]>: > 2008/11/12 Linas Vepstas <[EMAIL PROTECTED]>: > >> Yes, of course, the problem remains. > > Explanation: > > Thread 1 is the first thread that does any Guile stuff, so it loads > boot-9.scm, which means that it ends up in the (guile-user) module. > > Th

Re: bug: defining things in different threads

2008-11-20 Thread Linas Vepstas
2008/11/19 Neil Jerram <[EMAIL PROTECTED]>: > 2008/11/15 Linas Vepstas <[EMAIL PROTECTED]>: >> >> Well, originally, my code loaded a smob interface >> (defined a bunch of smobs) in thread 1, which I then >> found to be undefined in thread 2 (and all subsequent >> threads). Would your fix solve th

Re: bug: defining things in different threads

2008-11-19 Thread Neil Jerram
2008/11/15 Linas Vepstas <[EMAIL PROTECTED]>: > > Well, originally, my code loaded a smob interface > (defined a bunch of smobs) in thread 1, which I then > found to be undefined in thread 2 (and all subsequent > threads). Would your fix solve this? I guess yes if the problem was trying to refer

Re: bug: defining things in different threads

2008-11-15 Thread Linas Vepstas
Hi Neil, Thanks for the reply, 2008/11/15 Neil Jerram <[EMAIL PROTECTED]>: > 2008/11/12 Linas Vepstas <[EMAIL PROTECTED]>: > >> Yes, of course, the problem remains. > > Explanation: > > Thread 1 is the first thread that does any Guile stuff, so it loads > boot-9.scm, which means that it ends up i

Re: bug: defining things in different threads

2008-11-15 Thread Neil Jerram
2008/11/12 Linas Vepstas <[EMAIL PROTECTED]>: > Yes, of course, the problem remains. Explanation: Thread 1 is the first thread that does any Guile stuff, so it loads boot-9.scm, which means that it ends up in the (guile-user) module. Thread 2 hasn't done any (set-current-module ...), so it stay

Re: bug: defining things in different threads

2008-11-12 Thread Linas Vepstas
2008/11/12 Ludovic Courtès <[EMAIL PROTECTED]>: > Hi Linas, > > "Linas Vepstas" <[EMAIL PROTECTED]> writes: > >> void * scm_one (void *p) >> { >> prtdbg("thread one"); >> scm_c_eval_string ("(define x \"asddf\")\n"); >> } >> >> void * scm_two (void *p) >> { >> prtdbg("thread two")

Re: bug: defining things in different threads

2008-11-12 Thread Ludovic Courtès
Hi Linas, "Linas Vepstas" <[EMAIL PROTECTED]> writes: > void * scm_one (void *p) > { > prtdbg("thread one"); > scm_c_eval_string ("(define x \"asddf\")\n"); > } > > void * scm_two (void *p) > { > prtdbg("thread two"); > scm_c_eval_string ("(display x)\n"); > } AFAICS, the

bug: defining things in different threads

2008-11-11 Thread Linas Vepstas
Hi, I am finding that things defined in one thread are not always visible in another. This seems to be due to some threads having a different current-module than others. I think this is a bug. The example code below shows the issue. Help, comments appreciated. --linas /** * Guile threading b