The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Portability (was: BSDi Imaging)
Date: Mon, 27 Feb 2017 17:31:42 +1100	[thread overview]
Message-ID: <20170227063142.GD15516@eureka.lemis.com> (raw)
In-Reply-To: <3f132e39d3cca090ac41a0766c159548121f1e54@webmail.yaccman.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]

On Sunday, 26 February 2017 at 17:08:39 -0800, Steve Johnson wrote:
> I couldn't disagree more.

I think you could have :-) But thanks for the followup and the
details.

> Late in 1974, as I recall, Dennis mused "You know, I think it would
> be easier to move Unix to a new machine than to change a large
> application to run on another operating system."  I ... offered to
> write a portable C compiler.

By that time C on the PDP-11 had been round for a couple of years,
right?  And then you go on to be portable.  On the other hand, my
understanding of Algol and Cobol is that they didn't start with any
specific architecture in mind.  And it was that difference that I was
thinking of when I said that C wasn't designed to be portable.  A
matter of viewpoint, maybe.

I'm not belittling the design of C, nor your or Dennis' work, but
there's nothing you've said here that suggested that C was designed
from the outset to be portable.

> So C was indisputably intended to be portable, at least in that
> sense.  And in practice it was highly portable while sacrificing
> little in performance on different systems (unlike some other
> languages).

That certainly applied to the difference between C and Algol.  In
defence of Algol, it had no prior art to build on.

Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170227/94a9bec3/attachment.sig>


      reply	other threads:[~2017-02-27  6:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 12:50 [TUHS] BSDi Imaging Noel Chiappa
2017-02-26 20:49 ` [TUHS] Portability (was: BSDi Imaging) Greg 'groggy' Lehey
2017-02-27  1:08   ` Steve Johnson
2017-02-27  6:31     ` Greg 'groggy' Lehey [this message]

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=20170227063142.GD15516@eureka.lemis.com \
    --to=grog@lemis.com \
    /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).