January 7th, 2004

  • evan

(no subject)

One of my classes this quarter is all about making C more safe (yep, back to Cyclone again). His basic premise seems to be: we're never going to get rid of C because at the OS level, we need to be able to manage data and memory at the byte level and we need to be fast. But there are still ways to improve C's reliability without increasing the cost.

From the reading list under "array-bounds checking":
...I'm sorry to be politically incorrect, but for the ACM to then laud "C" and its inventors as a major advance in computer science has to rank right up there with Chamberlain's appeasement of Hitler.

  • evan


The other class I'm sitting in this quarter is CSE 501, the graduate compilers class. The undergrad compilers class covered pretty much everything in simple terms while glossing over optimization; this one seems to be focused on optimization, which apparently is where all the action is in compilers.

With that in mind, I'll also point out that raevnos directed me at this thread on the OCaml list, where someone found their program was 25-30% faster when they turned on bounds checking.