From: cym224 at gmail.com (Nemo)
Subject: [COFF] In Memoriam: Jay W. Forrester, happy birthday Gene Amdahl, and LSD
Date: Tue, 19 Nov 2019 18:17:29 -0500 [thread overview]
Message-ID: <CAJfiPzyy_8k3Moa9HAV=KYPvNhCMUXGWmPkhtFx64bSKQxO38g@mail.gmail.com> (raw)
In-Reply-To: <20191119202101.GF74610@server.rulingia.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On 19/11/2019, Peter Jeremy <peter at rulingia.com> wrote:
> On 2019-Nov-18 10:45:13 -0800, Bakul Shah <bakul at bitblocks.com> wrote:
>>Are you guys talking about “A formal description of System/360” by
>>Falkoff, Iverson and Sussenguth? It uses an APL like notation but not
>>exactly a S/360 emulator in APL! Much more concise than the S/360 POP.
>>
>>http://www.cs.trinity.edu/~jhowland/class.files.cs2321.html/falkoff.pdf
>
> I was referring to exactly that but didn't have the reference handy.
> Note that it's not "an APL like notation", it's the APL defined by Ken
> Iverson in "A Programming Language"[1]. And, no-one said it was an
> "emulator".
>
> [1] http://www.softwarepreservation.org/projects/apl/Books/APROGRAMMING%20LANGUAGE
>
> --
> Peter Jeremy
Blaauw and Brooks documented an enormous number of architectures that
way: https://www.pearson.com/us/higher-education/program/Blaauw-Computer-Architecture-Concepts-and-Evolution/PGM629.html
N.
>
next prev parent reply other threads:[~2019-11-19 23:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 21:54 dave
2019-11-15 22:26 ` krewat
2019-11-15 22:42 ` dave
2019-11-16 7:23 ` peter
2019-11-16 16:25 ` clemc
2019-11-17 5:14 ` dave
2019-11-18 16:42 ` clemc
2019-11-18 18:45 ` bakul
2019-11-18 19:19 ` clemc
2019-11-19 20:21 ` peter
2019-11-19 23:17 ` cym224 [this message]
2019-11-21 19:48 ` dave
2019-11-15 23:19 ` clemc
2019-11-15 23:47 ` krewat
-- strict thread matches above, loose matches on Subject: below --
2018-11-15 22:33 dave
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='CAJfiPzyy_8k3Moa9HAV=KYPvNhCMUXGWmPkhtFx64bSKQxO38g@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).