4 ms·
Annex K is optional.
by stephencanon 11y ago
Annex K is optional.
- pjmlp 11y agoHence why it is a joke. Not only has the standards comitte not done anything serious about preventing bounds overflows, they made it optional. Sizes still aren't guaranteed to be correct for the string/buffer. No portable C code can rely on its presence.
- stephencanon 11y agoAFAIK Annex K originated as a Microsoft proposal, so I find it somewhat strange that you're using it as an example of a C feature that Microsoft shouldn't adopt (though I agree that it's a terrible feature that never should have made the cut).
- pjmlp 11y agoYes, as such there is nothing to adopt. It is already there. What I am in favor is Microsoft pushing C aside. C++ provides safer constructs and if one wants to keep on doing unsafe C style coding, it is still there.