Re: [Chicken-users] Default buffering for output ports

2006-09-13 Thread felix winkelmann
On 9/12/06, Alejandro Forero Cuervo [EMAIL PROTECTED] wrote: Shouldn't the initial output port in Chicken applications be line-buffered? I think this is the standard practice in most programming languages, but it seems not to be the case with Chicken (I'm using 2.3 in GNU/Linux). In the

Re: [Chicken-users] Default buffering for output ports

2006-09-13 Thread Alejandro Forero Cuervo
Chicken does no buffering by itself, it just uses stdio routines,. These in turn call fputc() when writing characters or fputs() when writing strings. Everything else is handled on the C side. Ahh, you're right, as usual. I assumed some buffering was going on since I ran my tests in csi,

[Chicken-users] Default buffering for output ports

2006-09-12 Thread Alejandro Forero Cuervo
Shouldn't the initial output port in Chicken applications be line-buffered? I think this is the standard practice in most programming languages, but it seems not to be the case with Chicken (I'm using 2.3 in GNU/Linux). In the specific case of C, at least in GNU/Linux with glibc: The stream