I don't think it's a printf issue.
The statement
fprintf(f, "foo %d %f %d\n", 34, 12.0, 67);
prints
foo 34 0.000000 1076363264
so I'm inclined to think that the varargs handling is off after a %f.
Don't know what could cause this though.
Does anyone have a clue ?
Danny
On Mon, 2009-04-20 at 22:54 +0000, Pierre Ynard wrote:
>
>
> > But it works well if you leave out the -D__USE_MINGW_ANSI_STDIO=1 flag.
> >
> > So why are you trying to do this ?
>
> Without this flag, this program is dynamically linked against MSVCRT *printf
> functions, and those present a number of bugs, shortcomings (like, no support
> of %z modifiers) and weird, non-compliant behaviors (wrong return value,
> etc...),
> that we cannot fix. So the %f may work then, but a lot of other things (not
> shown in this test program) break.
>
> We tried patching the format string on the fly, but that's too much of a mess,
> or reimplementing compliant *printf functions, but mingw does just that for
> us.
> There is just this %f bug on WinCE.
>
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Cegcc-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
