News for hackers. Stuff that matters.
Re:Ode to the use-after-free: one vulnerable function, a tho... by pjmlp on Tuesday May 09, 2017 @12:54AM (#14297817)
Apparently this myth never dies.

Burroughs did not have this issue with ESPOL and NEWP almost 10 years earlier before C was born.

Nor did the UK Navy with Algol 68RS or the multiple institutes using PL/I variants.

Re:Ode to the use-after-free: one vulnerable function, a tho... by ktRolster on Tuesday May 09, 2017 @02:35AM (#14298151)
I'm going to suggest you didn't read my whole comment.
Re:Ode to the use-after-free: one vulnerable function, a tho... by pjmlp on Tuesday May 09, 2017 @03:07AM (#14298246)
I sure did.

Burroughs B5500 was created in 1961 and executed far slower and had less memory than a PDP-11, yet it was able to have a full OS written in ESPOL, an ALGOL dialect with intrisics for CPU instructions and explicit UNSAFE statements.

So if a 10 year old machine by the time C was created for computers with " extra overhead was unbearable." and " what you do when you have a 1Mhz computer" was already able to execute an Algol dialect with enough performance, what does that say of C in regards to language design?

Re:Ode to the use-after-free: one vulnerable function, a tho... by ktRolster on Tuesday May 09, 2017 @02:43PM (#14302775)
You have written nothing that indicates you've read my second paragraph.
Re:Ode to the use-after-free: one vulnerable function, a tho... by pjmlp on Tuesday May 09, 2017 @06:14PM (#14304280)
Only if you implying that people that wrote operating systems before C was designed, were lazy and didn't care about performance, in spite of having less powerful hardware at their disposal.