-[ Thu, Nov 10, 2011 at 12:16:38AM +0100, Andy Wingo ]
> > Indeed, it would probably need per-port mutexes, making I/O primitives
> > thread-safe by default, and perhaps providing unlocked variants like
> > libc does.
>
> I did this in master, but something was going wrong so I stubbed it out
On Sun 21 Aug 2011 15:22, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> Oh dear, this is a nasty one. The issue is that Guile's ports are not
>> threadsafe. I hadn't thought about this one...
>>
>> I am adding guile-devel to the Cc for input. Any fix to this will be
>> pret
Update of bug #33996 (project guile):
Status:None => Fixed
Open/Closed:Open => Closed
___
Follow-up Comment #1:
I think I have fixed
Hi!
Andy Wingo skribis:
> Oh dear, this is a nasty one. The issue is that Guile's ports are not
> threadsafe. I hadn't thought about this one...
>
> I am adding guile-devel to the Cc for input. Any fix to this will be
> pretty big, I think. I think that the right fix here is probably what
>
On Thu 18 Aug 2011 15:42, ri...@happyleptic.org writes:
> -[ Thu, Aug 18, 2011 at 11:36:37AM +0200, Andy Wingo ]
>> Oh dear, this is a nasty one. The issue is that Guile's ports are not
>> threadsafe. I hadn't thought about this one...
>
> Aren't they supposed to be? I though that was what s
-[ Thu, Aug 18, 2011 at 11:36:37AM +0200, Andy Wingo ]
> Oh dear, this is a nasty one. The issue is that Guile's ports are not
> threadsafe. I hadn't thought about this one...
Aren't they supposed to be? I though that was what scm_i_port_table_mutex
was there for.
Hi Cedric,
On Fri 12 Aug 2011 09:42, Cedric Cellier writes:
> (use-modules (ice-9 threads))
>
> (define (forever f)
> (f)
> (forever f))
>
> ; Spawn a thread that performs some writes
> (make-thread forever (lambda ()
>(display "write...\n")))
>
> (forever (lambda ()
