Hacker News Reader

but here in the case of Microsoft Checked C , you still need to modify your actual source code to get safer one.

But you're moving to a safer subset, not a safer superset, so it still shouldn't require significant alterations.

Uhhh moving from set to subset is what requires alterations, set to superset does not, by definition.

The problem here is compiler support and performance.

C++ is an altered and extended form of C, thus I would say it is more accurate to call it a superset, rather than a subset. I'm not using precise definitions here.

And of course, but those will come in time. The point of it is that C++ isn't any safer (And actually, I would say is more risky in some aspects, because of the differences between (For example) the UB in C and C++), while Checked C is guaranteed to be safer, to a certain degree.

OK, I have to admit that Checked C is probably strictly safer while C++ is ... a mixed thing (both safer and more complicated).

Reply on news.ycombinator.com