在 2019/1/3 23:05, Jacek Caban 写道:
> 
> We could, but that's not my point. If other toolchain always declare
> those extensions in C++, this practically becomes a standard that may
> make sense for us to follow.
> 

Most of such things are part of the POSIX standard. But as you have
pointed out latter, GNU developers consider the introduction of
`_GNU_SOURCE` 'a wart', so I am still a bit against this patch.

>> I grep'd over libstdc++ headers for `M_PI` and found no results. Which
>> declaration was it that caused the failure?
> 
> 
> I chose M_PI as an example. It's not libstdc++ that caused issues in
> cases I mentioned, it's a similar assumption in Mozilla code. See:
> 
> https://gcc.gnu.org/onlinedocs/libstdc++/faq.html#faq.predefined
> 
> for an explanation about libstdc++.
> 

Then Mozilla people are wrong and should fix their code to either 0)
compile in a POSIX-conforming mode rather than an ISO-conforming mode,
or 1) remove references to non-ISO symbols or macros.

> 
> Thanks,
> 
> Jacek


-- 
Best regards,
LH_Mouse

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to