The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Michael Kjörling" <michael@kjorling.se>
To: tuhs@tuhs.org
Subject: Re: [TUHS] c's comment
Date: Fri, 7 Dec 2018 14:06:35 +0000	[thread overview]
Message-ID: <20181207140635.nlwngnu5alrqnekn@h-174-65.A328.priv.bahnhof.se> (raw)
In-Reply-To: <20181207083154.ucpd6qim3ghclfhn@crack.deadbeast.net>

On 7 Dec 2018 03:31 -0500, from g.branden.robinson@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
issue.

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

-- 
Michael Kjörling • https://michael.kjorling.se • michael@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)

  parent reply	other threads:[~2018-12-07 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07  4:27 Caipenghui
2018-12-07  8:31 ` G. Branden Robinson
2018-12-07  9:53   ` Caipenghui
2018-12-07 14:06   ` Michael Kjörling [this message]
2018-12-07 15:01 Richard Tobin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181207140635.nlwngnu5alrqnekn@h-174-65.A328.priv.bahnhof.se \
    --to=michael@kjorling.se \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).