From: Dr Iain Maoileoin <iain@csp-partnership.co.uk>
To: Mike Markowski <mike.ab3ap@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Algol 68 and Unix (was cron and at ...)
Date: Thu, 17 Dec 2020 21:18:33 +0000 [thread overview]
Message-ID: <AAD0555D-2530-40B7-A4B7-5FA31C0ECA56@csp-partnership.co.uk> (raw)
In-Reply-To: <39730a23-090d-0a03-a536-aa83d5f7dc6f@gmail.com>
> On 17 Dec 2020, at 14:44, Mike Markowski <mike.ab3ap@gmail.com> wrote:
>
> On 12/17/20 9:21 AM, M Douglas McIlroy wrote:
>> ...My knowledge of A68 comes from reading the official definition back in
>> the day. It took effort to see the clarity of the design through the
>> fog of the description. Until more accessible descriptions came along
>> (which I admit to not having seen) it would have been a big barrier to
>> acceptance...
>
> By coincidence, fortune brought this up as I opened a terminal window:
>
> No proper program contains an indication which as an operator-applied occurrence identifies an operator-defining occurrence which as an indication-applied occurrence identifies an indication-defining occurrence different from the one identified by the given indication as an indication-applied occurrence.
> -- ALGOL 68 Report
Now that I understand ;-)
> Yikes…
But that bit I dont! ;-(
> Mike
We we taught Algol 68 R, running it on an ICL 1904S from 1st year onwards. The 1904 was a 24bit 6 bits per “byte” system. Handling upper and lower on the line printer was a lot of work!
The mixture of language practical and theory helped cement both. Unix did not come along - for the uni - until a year or so later.
A decent understanding of the Algol68 pointers, deref (auto or not), casts, array slices, garbage collection etc made moving to C fairly easy for most of the cohort.
The fortune cooked has been a bad journalist and taken the sentence out of context. The previous 423 pages were essential reading.
next prev parent reply other threads:[~2020-12-17 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 14:21 M Douglas McIlroy
2020-12-17 14:24 ` Ronald Natalie
2020-12-17 14:35 ` Larry McVoy
2020-12-17 14:44 ` Mike Markowski
2020-12-17 21:18 ` Dr Iain Maoileoin [this message]
2020-12-18 5:06 ` John Cowan
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=AAD0555D-2530-40B7-A4B7-5FA31C0ECA56@csp-partnership.co.uk \
--to=iain@csp-partnership.co.uk \
--cc=mike.ab3ap@gmail.com \
--cc=tuhs@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).