On 2017/5/16 0:43, Vincent Lefevre wrote:
> On 2017-05-15 22:35:33 +0800, Liu Hao wrote:
>> Yeah but `printf()` from glibc doesn't think it is a NaN... From
>> your point of view, is this a glibc bug?
>
> I think so. If I understand correctly, the output of floating-point
> data in glibc is handle
If I were a mingw-w64 committer, I probably wouldn't make that change,
but I am OK with it. An argument in favor of that change is that it
isn't too hard to just use sed or carefully-placed #defines to fix any
Microsoft-style code that uses __in and __out. (It's not ideal, but
not terrible.) And
W dniu 2017-05-15 o 08:51, Liu Hao pisze:
> On 2017/5/11 23:11, Kai Tietz wrote:
>> I would prefer this too, but I don't believe that we can convince
>> libstdc++ maintainers to modify their code for this. Sadly the MS'
>> platform sdk defines a lot of stuff, which collides some times with
>> some
