2 ms·
The number of people I have interviewed that have used C and C++ for years and can't tell me what undefined behavior is is too damned high. I've had one or two
by Espressosaurus 4y ago
The number of people I have interviewed that have used C and C++ for years and can't tell me what undefined behavior is is too damned high. I've had one or two, and only one of them could give me a coherent answer of what the compiler is allowed to do if it runs across it.
In my experience it's only the language lawyers who actually know what to look out for, and there are damned few of them.
Which is stupid since undefined and unspecified behaviors are hugely important to how C and C++ are used in the field.
- waiseristy 4y agoWe’ve been really spoiled by modern compilers and operating systems which let you get away with large swaths of undefined behavior. You typically don’t know what is hidden from you
- simplotek 4y ago> Which is stupid since undefined and unspecified behaviors are hugely important to how C and C++ are used in the field. Is it really that fundamental if you can setup your project to throw warnings/errors, and even use static code analysis tools to flag those? I'd argue that it's far worse to work on a project that's not setup to detect those errors than to expect that sort of issue to be handled at the recruiting level.
- scotty79 4y ago> Which is stupid since undefined and unspecified behaviors are hugely important to ... Why are they though? Should they be?