This is supposed to be the compiler of the future?https://twitter.com/ch3root/status/735844188101726208 …
Only if there's a unified option for "adhere to the standard" rather than N different esoteric ones you have to know
-
-
Yeah, let's introduce an option to choose a particular standard, like -std=c11. Oh, wait... :-)
-
Exactly. My point was that the standards-conforming options should all be implied by -std=c11, etc.
-
if a vuln was found in a standard should we require extra flags to disable feature, should it be default?
-
I don't know what "a vuln in the standard" would look like.
-
AFAICT it's a meaningless term. The closest thing might be funcs like "gets" that are impossible to use right.
-
But then the only fix is teaching programmers not to use them, or amending the standard to remove them.
-
right I'm in favor of the latter. Default insecurity through backwards compatible standards needs to stop
End of conversation
New conversation -
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.