News for hackers. Stuff that matters.

A comment on A Guide to Undefined Behavior in C and C++ (2010). Parent comment

Re:A Guide to Undefined Behavior in C and C++ (2010) by pjmlp on Sunday November 04, 2018 @04:29AM (#18375033)
We are entitled to be emotional about it, because we all have to use tools which have the misfortune to be written in C derived languages.

Even if I don't touch those languages for production code, my whole stack safety is dependent how well those underlying layers behave, and how responsibile the developers were towards writing secure core.

Which as proven by buffer oveflows in IoT devices not much.

[ Parent | on HN ]
Re:A Guide to Undefined Behavior in C and C++ (2010) by xmiller on Sunday November 04, 2018 @05:27AM (#18375198)
So where is your production code written in Ada or Pascal?
[ Parent | on HN ]
Re:A Guide to Undefined Behavior in C and C++ (2010) by pjmlp on Sunday November 04, 2018 @06:36AM (#18375379)
Ada cannot tell.

Pascal was replaced by Java and C#.

[ Parent | on HN ]
Re:A Guide to Undefined Behavior in C and C++ (2010) by jacoblambda on Sunday November 04, 2018 @12:19PM (#18376877)
Ada absolutely can tell. Divide by zero throws an exception and buffer overflows are caught by essentially every modern compiler.
[ Parent | on HN ]
Re:A Guide to Undefined Behavior in C and C++ (2010) by pjmlp on Sunday November 04, 2018 @01:49PM (#18377409)
Sure it can, but that wasn't the question. Rather what happened to the code I have written.

NDAs make us not able to tell about stuff.

What magic variant of C or C++ compiler are you using that throws errors on buffer corruption, unless you are speaking about using code with debugging mode enabled in production instead of using a proper release build.

[ Parent | on HN ]
Re:A Guide to Undefined Behavior in C and C++ (2010) by jstimpfle on Sunday November 04, 2018 @12:47PM (#18377048)
> buffer overflows are caught by essentially every modern compiler.

If you use high-level arrays with bounds-checking, which are not always fast enough, and can become a maintenaince burden. If they should be absolutely secure (like, std::vector isn't - it can be moved behind your back), they also require GC.

[ Parent | on HN ]