3 ms·
Good question :) I think it did, though I'd be interested to hear an informed opinion.
by paulddraper 10y ago
Good question :) I think it did, though I'd be interested to hear an informed opinion.
- solidsnack9000 10y agoI, for one, see C as both unsafe and unergonomic. The many features of C++ can be seen as various attempts to make some or another thing expressible in C -- parameterized datatypes, namespacing, encapsulated resource management -- that wasn't before.
- pjmlp 10y agoIt is, after being forced to use BCPL to finish his PhD and being used to languages like Simula, Bjarne swore he wouldn't be doing that again. Hence why he started to design C with Classes after getting his job at AT&T. https://www.youtube.com/watch?v=ZO0PXYMVGSU https://www.youtube.com/watch?v=ZO0PXYMVGSU Around 29:00.
- pjmlp 10y agoFrom Dennis himself, https://www.bell-labs.com/usr/dmr/www/chist.html https://www.bell-labs.com/usr/dmr/www/chist.html The best part for those that care about security: "To encourage people to pay more attention to the official language rules, to detect legal but suspicious constructions, and to help find interface mismatches undetectable with simple mechanisms for separate compilation, Steve Johnson adapted his pcc compiler to produce lint [Johnson 79b], which scanned a set of files and remarked on dubious constructions." So although C designers saw the dangers of C and provided static analysis from the early days, many C developers keep ignoring them.