Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS] Unix quix
Date: Thu, 23 Jan 2020 09:31:10 -0500	[thread overview]
Message-ID: <CAC20D2NX0DK5w-8LGOjzdGzVRZ+r1bF5xPyjbEJJVoAqT9Q4dQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OiPLpUQkezbG_JS-Jr20VCzM9ZgBsHAMBe-LYi4wMk6w@mail.gmail.com>

BTW:  Not to bring up a new rat hole/new argument, but rather remind people
of one of the arguments of the day.  Because of SP or no SP style of
calling, in those days the question came out language design of how the
stack or register call area was maintained:  Was it/should it be the
responsibility of the calling routine or the called subroutine.  Things
like Fortran's entry statement and other non-local goto's,
co-routines/setjmp/longjmp added fuel to the fire in the argument.

As a language designer/implementor at the time, someone like Steve Johnson
and Doug McIlroy were undoubtedly mixed up in the argument and had
opinions.  I was certainly too inexperienced then to understand what the
fight was about.   But I do remember the fight and how the issues were
taught/discussed at CMU when I was a student.  I admit I was quickly sucked
into C's way of handling things, as it seemed simple/clear/understandable
to me, but not being a language person I probably did not (maybe still do
not) value some the arguments for the other side.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200123/2f617b8b/attachment.html>


  reply	other threads:[~2020-01-23 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200122184244.14CBB18C083@mercury.lcs.mit.edu>
2020-01-23  5:27 ` peter
2020-01-23 14:08   ` clemc
2020-01-23 14:31     ` clemc [this message]
2020-01-23 15:51       ` doug
2020-01-25  0:09         ` bakul
2020-01-24  1:18   ` krewat

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=CAC20D2NX0DK5w-8LGOjzdGzVRZ+r1bF5xPyjbEJJVoAqT9Q4dQ@mail.gmail.com \
    --to=coff@minnie.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).