> -----Original Message----- > From: Koehne Kai [mailto:[email protected]] > Sent: Friday, May 03, 2013 2:29 PM > To: [email protected] > Subject: Re: [Mingw-w64-public] format check broken > > > > > -----Original Message----- > > From: Ozkan Sezer [mailto:[email protected]] > > Sent: Friday, May 03, 2013 2:12 PM > > To: [email protected] > > Subject: Re: [Mingw-w64-public] format check broken > > > > [...] > > Even then, it affects libstdc++ compilation itself. IMO, mingw[-w64] > > should not default to __USE_MINGW_ANSI_STDIO=1 by itself and leave > the > > decision to user (which is what we already do at present.) > > Since all newer versions of MSVC runtimes support e.g. %lldb
I mean %lld, of course. Actually I am compiling lldb in the background, but for entirely different reasons ... > I think having > an ANSI compliant default would make IMO even more sense. > > Anyhow, isn't the problem that gcc on windows still defaults to win_printf? It's called ms_printf. :) > So even if your printf supports %lldb, it'll warn about it? ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
