News for hackers. Stuff that matters.

A comment on On the history and justification of the C programming language. Parent comment

Re:On the history and justification of the C programming lan... by catnaroek on Thursday August 18, 2016 @01:52PM (#12314764)
> Our code was malloc once, free never. Dangling pointers were by definition impossible.

Dangling pointers can arise in other ways: use an uninitialized pointer variable, take the wrong offset from an otherwise valid pointer, etc.

[ Parent | on HN ]
Re:On the history and justification of the C programming lan... by vonmoltke on Thursday August 18, 2016 @02:09PM (#12314951)
Those are indeterminate values but they aren't dangling pointers. Dangling pointers are specifically references to an object that has been freed.

Plus, the cases you highlighted are programming errors, not reliance on undefined behavior.

[ Parent | on HN ]