On Jun 6, 2020, at 1:49 PM, Ed Carp <erc(a)pobox.com> wrote:
On 5/27/20, Ronald Natalie <ron(a)ronnatalie.com> wrote:
The large areas of undefined and unspecified
behavior has always been an
issue in C. It was somewhat acceptable when you were using it as a direct
replacement for assembler, but Java and many of other follow-ons endevaored to be more
portable/rigourous. Of course, you can write crap code in any language.
"It's not a bug, it's a feature"
A snippet of a recent comp.arch post by someone (the subject was C and safety):
What you call "misfeatures", some other people call "features". If
expect people to take you and your opinions seriously, you'll get on
better if you stop mocking other opinions. I've written several times
why undefined behaviour lets me write better and safer code, as well as
more efficient code. If you remain determinedly unconvinced, at least
agree to disagree without sounding childish about it.