Re: [Mingw-users] Re: libc bug report

[<mi...@ca...>]

Interesting, sorry if I failed to know the most basic C rules.
Changing

fputc(0x20,file);  // where does this come in the result file??????

to

fseek(file,0,SEEK_CUR);
fputc(0x20,file);  // aah, there it is!!!!!

solved the problem.

Having fflush(file) instead of the fseek was moving the file pointer to the
end of the file, which I dont fully
understand. Do you have an explanation for that too?


/Anders


----- Original Message -----
From: "Oscar Fuentes" <of...@wa...>
To: <min...@li...>
Cc: <mi...@ca...>
Sent: Sunday, July 25, 2004 11:20 PM
Subject: [Mingw-users] Re: libc bug report


> Anders Lindén <mi...@ca...> writes:
>
> [snip]
>
> >   for (int i=0; i<8; i++)
> >     fgetc(file);
> >
> >   fputc(0x20,file);  // where does this come in the result file??????
>
> From the C Standard:
>
> 7.19.5.3/6
> When a file is opened with update mode [...] However, output
> shall not be directly followed by input without an intervening call to
> the fflush function or to a file positioning function (fseek, fsetpos,
> or rewind), and input shall not be directly followed by output without
> an intervening call to a file positioning function, unless the input
> operation encounters end-of-file.
>
> [snip]
>
> --
> Oscar
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> MinGW-users mailing list
> Min...@li...
>
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users