During discussion about inttypes I realized that we check (in header files) if
__USE_MINGW_ANSI_STDIO is active in non consistent way:
#if defined(__USE_MINGW_ANSI_STDIO) && ((__USE_MINGW_ANSI_STDIO + 0) != 0)
#elif defined(__USE_MINGW_ANSI_STDIO)
#if !defined (__USE_MINGW_ANSI_STDIO) ||
We had a discussion about it and I'd like to get it back to the patch. I
tested it some more and I think it's ready. Please review the patch.
There was a concern that applications might define
__USE_MINGW_ANSI_STDIO but instead of including stdio.h obtaining a
declaration in another way, ending
On 10/31/2018 03:32 AM, Liu Hao wrote:
> 在 2018/10/31 2:01, Jacek Caban 写道:
>> Wine has a test for that with a comment saying that it's supported since
>> Vista:
>> https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/msvcrt/tests/printf.c#l291
>>
>>
>> I changed the test to accept only
在 2018/10/31 21:53, Earnie via Mingw-w64-public 写道:
> Is it possible to allow a skip for the test if the test machine doesn't
> support that test? Or is that what Jacek did?
>
As far as I can see hijacking the test was only a means of discovering
platforms whose MSVCRT.DLL has a `printf()` that
On 10/30/2018 10:32 PM, Liu Hao wrote:
> 在 2018/10/31 2:01, Jacek Caban 写道:
>> Wine has a test for that with a comment saying that it's supported since
>> Vista:
>> https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/msvcrt/tests/printf.c#l291
>>
>>
>> I changed the test to accept only
