3 ms·
"Which is pretty much my point: You don't like C, because it didn't take from Wirth enough." Close but not there yet. He doesn't like C because it ignored and
by nickpsecurity 10y ago
"Which is pretty much my point: You don't like C, because it didn't take from Wirth enough."
Close but not there yet. He doesn't like C because it ignored and still ignores basic, safety features on commonly-used operations. Wirth's stuff is often cited because it did safe one's as baseline, simple syntax/semantics, and for weak hardware. Closer to C than ALGOL, PL/0, and other languages we could cite that also had more safety. Telling a C programmer Thompson and Ritchie could've done ALGOL68 on a PDP-7 less believable than saying they could've done Modula-2 or something similar. ;)
Note: I also can't overemphasize enough that the first language they actually designed, feature by feature, to replace C was a modification of Wirth's Oberon-2 with features like we're talking about. Their Go work is indeed reducing number of crashes and vulnerabilities in systems versus C work while performing fast and improving. Imagine if they just started with Wirth's stuff then kept it practical and long-lasting (unlike Wirth).
- qwertyuiop924 10y ago>Note: I also can't overemphasize enough that the first language they actually designed, feature by feature, to replace C was a modification of Wirth's Oberon-2 with features like we're talking about. No... The first language they designed to replace C was Plan9 C. Then Go, which drew heavy inspiration from Limbo, apparently.
- nickpsecurity 10y agoI hadn't heard there was a different version of C for Plan 9. Got a link showing differences/advantages?
- qwertyuiop924 10y agohttp://doc.cat-v.org/plan_9/programming/c_programming_in_plan_9 http://doc.cat-v.org/plan_9/programming/c_programming_in_pla... It's mostly ANSI C, but with some variations (you can only #include once), and a lot of work put into ensuring portability without #ifdef and auto*.