From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Portability (was: BSDi Imaging)
Date: Mon, 27 Feb 2017 07:49:00 +1100 [thread overview]
Message-ID: <20170226204900.GC15516@eureka.lemis.com> (raw)
In-Reply-To: <20170226125050.9691E18C09B@mercury.lcs.mit.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
On Sunday, 26 February 2017 at 7:50:50 -0500, Noel Chiappa wrote:
>
> There were in theory portable languages beforehand (e.g. PL/1), but
> I think it probably over-specified things - e.g. it would be
> impossible to port Multics to another architecture without almost
> completely re-writing it from scratch, the code is shot through with
> "fixed bin(18)"'s every other line...
That may be coloured by your perspective. C was never designed to be
portable, while much older languages like Algol and Cobol were. There
were quite different reasons for C's success.
To quote "The Programmer's ABC's†from Datamation, April 1976:
C is for Cobol
What a pity
It was designed
By a committee
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/6664de35/attachment-0001.sig>
next prev parent reply other threads:[~2017-02-26 20:49 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 ` Greg 'groggy' Lehey [this message]
2017-02-27 1:08 ` [TUHS] Portability (was: BSDi Imaging) Steve Johnson
2017-02-27 6:31 ` Greg 'groggy' Lehey
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=20170226204900.GC15516@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).