[TUHS] c's comment

Michael Kjörling michael at kjorling.se
Sat Dec 8 00:06:35 AEST 2018

On 7 Dec 2018 03:31 -0500, from g.branden.robinson at gmail.com (G. Branden Robinson):
> Back in the old days (1993!) a freshman programmer on SunOS 4 would be
> subjected to a truly incomprehensible chain of compiler errors that
> arose from a single lexical mistake like a missing semicolon.

That's around the time when I first started dabbling in C. One of the
first things I figured out was that it was a great help to ignore all
errors but the first one if I got a slew of errors during compilation;
figure out how to fix that first one, recompile, and see if the other
errors went away. Usually, they did. Thankfully, the programs I was
working on at the time were small, so compilation time wasn't an

I think that advice was even in one of the books I was (trying to)

Michael Kjörling • https://michael.kjorling.semichael at kjorling.se
  “The most dangerous thought that you can have as a creative person
              is to think you know what you’re doing.” (Bret Victor)

More information about the TUHS mailing list