-
-
-
@stephentyrone@RichFelker, I am looking forward to discuss that on the next meeting, let's see if there will still be somebody defending it
End of conversation
New conversation -
-
-
@RichFelker Annex K is about bounds checking, right ? Why the removal ? -
@Palsenberg Annex K is Microsoft's *_s functions which are poorly designed and have lots of practical problems. See http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm … -
@Palsenberg Basically the latest round of MS throwing a wrench in the process for a standard they try to control but refuse to implement.
End of conversation
New conversation -
-
-
@RichFelker @spun_off "(pathlen += filelen) < pathlen" no good, no sequence point ...but the _s version prevents exploitability :) -
@comex @spun_off Yes, several ppl have found bugs. Wish they ran the report by some friendly proofreaders first. I would have been happy to. -
@RichFelker @spun_off I'm glad they didn't, because the bug demonstrates the usefulness of being paranoid even when it seems redundant. -
@comex @spun_off Yes but people are just going to use it to detract from the credibility of the report, when the key points are sound... -
@RichFelker @spun_off Personally I found it a mix of good points and crap. As is the API itself...
End of conversation
New conversation -
-
-
@RichFelker @spun_off One of that paper's examples of a safe program that suffers from having to use _s... is, AFAICT, actually unsafe!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.