[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] [PATCH] Disable getc_unlocked on MinGW
|
From: |
Peter Bex |
|
Subject: |
Re: [Chicken-hackers] [PATCH] Disable getc_unlocked on MinGW |
|
Date: |
Wed, 29 Apr 2015 21:37:42 +0200 |
|
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Tue, Apr 28, 2015 at 08:57:54PM +1200, Evan Hanson wrote:
> As noted by Matt Gushee on address@hidden
Why are we even using the unlocked versions? They're thread-unsafe,
which means, if I understand correctly, that if you use CHICKEN with
for example the concurrent-native-callbacks egg, any code reading
from stdin is liable to break.
Is it for performance? Is the impact big enough to matter?
Otherwise I'd vote to just use plain old standard getc().
Cheers,
Peter
signature.asc
Description: Digital signature