This is *still* getting asked and gcc *still* has not fixed it, in 2018. 29 years after it was officially a bug.https://stackoverflow.com/q/51807085/379897 …
-
-
Replying to @RichFelker
Errr, reading the question it’s officially *not* a bug
1 reply 0 retweets 0 likes -
-
-
Replying to @o_galibert
Right, at some point it was fixed not to do it in standards-conformance modes. However, these macro names are so egregiously clashing that they shouldn't be defined ever; they break lots of real, reasonable code.
2 replies 0 retweets 0 likes -
Replying to @RichFelker
I tend to agree, but it’s a (stupid but backwards compatible) feature, not a bug
1 reply 0 retweets 0 likes
Replying to @o_galibert
Anything depending on a "feature" that backwards is going to have much bigger problems moving to a modern compiler version.
12:41 PM - 12 Aug 2018
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.