OK, applied this as rev. 1395: http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64?view=rev&revision=1395 Please test.
-- Ozkan On Sat, Sep 19, 2009 at 1:41 PM, Ozkan Sezer <seze...@gmail.com> wrote: > On Sat, Sep 19, 2009 at 1:38 PM, Kai Tietz <ktiet...@googlemail.com> wrote: >> Ok, add it to our _mingw.h file, too. We can then simplify our logic > > Will do. > >> in our _mingw_printf_(push/pop).h headers, too, as we know that >> __USE_MINGW_ANSI_STDIO is defined in any case to zero or one, isn't >> it? > > If you are referring to the rev. 1377 change, I wouldn't rely > on it being definitely defined as 0 or 1. User may be buggy > and would just do -D__USE_MINGW_ANSI_STDIO without > an =0 or =1, would he not? > >> >> Cheers, >> Kai > > -- > Ozkan > >> 2009/9/19 Ozkan Sezer <seze...@gmail.com>: >>> On Sat, Sep 19, 2009 at 1:13 PM, Erik de Castro Lopo >>> <mle+...@mega-nerd.com> wrote: >>>> Ozkan Sezer wrote: >>>> >>>>> You need it with both. (Although, if your w32 toolchain is >>>>> a mingw.org toolchain and not ours, they may have automatically >>>>> defined __USE_MINGW_ANSI_STDIO as 1 upon seeing -std=c99. Kai, >>>>> should we do that?) >>>> >>>> Yes, please! >>>> >>>> Cheers, >>>> Erik >>>> -- >>> >>> Hmm this is what the mingw.org guys do in their _mingw.h: >>> >>> #ifndef __USE_MINGW_ANSI_STDIO >>> /* >>> * If user didn't specify it explicitly... >>> */ >>> # if defined __STRICT_ANSI__ || defined _ISOC99_SOURCE \ >>> || defined _POSIX_SOURCE || defined _POSIX_C_SOURCE \ >>> || defined _XOPEN_SOURCE || defined _XOPEN_SOURCE_EXTENDED \ >>> || defined _GNU_SOURCE || defined _BSD_SOURCE \ >>> || defined _SVID_SOURCE >>> /* >>> * but where any of these source code qualifiers are specified, >>> * then assume ANSI I/O standards are preferred over Microsoft's... >>> */ >>> # define __USE_MINGW_ANSI_STDIO 1 >>> # endif >>> #endif >>> >>> (FWIW, we can also check for _POSIX for consistency with >>> other parts of our headers, too.) >>> >>> Kai, we can add it to our _mingw.h, too. What do you think? >>> Can this kind of thing cause any incompatibilities when a >>> piece of software is compiled with -std=c99 or -std=gnu99 ? >>> >>> -- >>> Ozkan > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
