Expected behaviour of fgets on stdin after a EOF ?

Hi, I've found a difference between the cygwin implementation of fgets and the ones I use on Win32, Linux (debian, libc-2.3.2) and Solaris (2.7) boxes. The following example illustrates the difference of behavior: #include int main() { char dst[256]; printf(">"); while(1) { if (fgets

RE: Expected behaviour of fgets on stdin after a EOF ?

> -Original Message- > From: cygwin-owner On Behalf Of Laurent Lagosanto > Sent: 18 October 2004 18:48 > Am I doing something wrong with fgets ? What part of "END of file" don't you get? cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info:

[OT] RE: Expected behaviour of fgets on stdin after a EOF ?

> -Original Message- > From: cygwin-owner On Behalf Of Dave Korn > Sent: 18 October 2004 18:54 [ OT tagged, because this is all standard c programming / library / posix stuff and not cygspecific. If you want to discuss further, http://cygwin.com/acronyms#TITTTL! ] > > -Original Mess

Re: [OT] RE: Expected behaviour of fgets on stdin after a EOF ?

On Mon, Oct 18, 2004 at 07:09:11PM +0100, Dave Korn wrote: > For the serious answer, see the SUS definition of fgets... > > http://www.opengroup.org/onlinepubs/009695399/functions/fgets.html > > (although for preference you really want to refer to the C language spec, to > which the SUS defers: