4 ms·
>C was developed between 1969 and 1973, making it nearly 40 years old [...] C ha[s] already made an exceptionally good start on a century-long reign In all fai
by zeteo 15y ago
>C was developed between 1969 and 1973, making it nearly 40 years old [...] C ha[s] already made an exceptionally good start on a century-long reign
In all fairness, development continued past 1973. Most C programmers today would have some trouble even reading the code from the 1978 first edition of K&R; and the void* pointer, that the author refers to later in the article, was a part of ANSI C (~1990).
- DiabloD3 15y agoDevelopment on C hasn't stopped. C1x is coming soon (probably 2012 or 13), and has a lot of interesting enhancements including bounds checking.
- cygx 15y agoAccording to Herb Sutter's obit for Dennis Ritchie ( http://herbsutter.com/2011/10/12/dennis-ritchie/ http://herbsutter.com/2011/10/12/dennis-ritchie/ ), C1x already passed its final ballot, so all that's missing is an official announcement. It would be nice to know if there are any changes from the April draft, though...
- comex 15y agoBounds checking is just for library functions, and there isn't something like automatic array bounds checking, right? Still, whoa - > #define cbrt(X) _Generic((X), long double: cbrtl, \ > default: cbrt, \ > float: cbrtf)(X) Fun stuff.
- LukeShu 15y agoDefinitely. Occasionally I'll run across some code in an old program (eg: Emacs), and be utterly unable to read it, because it's an older dialect of C (that I'm surprised most compilers still accept). I'll have to dig out a copy of K&R first edition just to read the code.