why would I want to use __mingw_printf? what exactly is it? why shouldn't I
just use printf like I think I should (end-user's prospective)? normally I
would see that and assume it's some sort of internal compiler-use thing and
avoid it and just stick with the the standard c library or c++ library stuff.
this is news to me, and I have been working with mingw-w64 for a few years now
- lost count. new feature?
>________________________________
> From: JonY <jo...@users.sourceforge.net>
>To: mingw-w64-public@lists.sourceforge.net
>Sent: Monday, June 10, 2013 3:06 AM
>Subject: Re: [Mingw-w64-public] PRIu64 and uint64_t
>
>
>On 6/10/2013 14:07, Jim Michaels wrote:
>> is there a way to detect compilation with --ansi or --posix?
>>
>
>No, this should not be needed, the correct inttypes macro will be used
>corresponding to the printf set. C99 printf with __mingw_printf etc...
>
>I have not investigated this further.
>
>
>
>------------------------------------------------------------------------------
>How ServiceNow helps IT people transform IT departments:
>1. A cloud service to automate IT design, transition and operations
>2. Dashboards that offer high-level views of enterprise services
>3. A single system of record for all IT processes
>http://p.sf.net/sfu/servicenow-d2d-j
>_______________________________________________
>Mingw-w64-public mailing list
>Mingw-w64-public@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
