From: Paul Ruizendaal <pnr@planet.nl>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Blit source
Date: Thu, 19 Dec 2019 10:09:52 +0100 [thread overview]
Message-ID: <AC1798F2-2248-4751-93D2-73C2166D4A44@planet.nl> (raw)
> If 5620s were called Jerqs, it was an accident. All the software with that
> name would be for the original, Locanthi-built and -designed 68K machines.
>
> The sequence is thus Jerq, Blit, DMD-5620
Maybe the “Jerq” name had a revival. If the processor switch came with some upheaval it is not hard to see how that revival could have happened.
The Dan Cross tar archive with the source code has two top level directories, one named “blit" with the 68K based source and another one named “jerq" with the Bellmac based source. The tar archive seems to have been made in the summer of 1985, or at least those dates are on the top level directories.
I am of course not disputing that the original name was Jerq. There are many clues in the source supporting that, among which this funny comment in mcc.c:
int jflag, mflag=1; /* Used for jerq. Rob Pike (read comment as you will) */
next reply other threads:[~2019-12-19 9:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 9:09 Paul Ruizendaal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-06 21:01 Norman Wilson
2019-12-19 0:16 Norman Wilson
2019-12-19 0:26 ` Rob Pike
2019-12-19 3:47 ` Mike Haertel
2019-12-19 6:49 ` Angelo Papenhoff
2019-12-19 5:12 ` Dan Cross
2019-12-19 6:54 ` Rob Pike
2019-12-19 8:03 ` arnold
2019-12-19 15:32 ` Chet Ramey
2019-12-15 20:45 Paul Ruizendaal
2019-12-15 21:17 ` Angelo Papenhoff
2019-12-16 6:25 ` emanuel stiebler
2019-12-16 11:06 ` Paul Ruizendaal
2019-12-17 6:04 ` emanuel stiebler
2019-12-18 3:53 ` Paul Ruizendaal
2019-12-18 4:30 ` Rob Pike
2019-12-18 10:43 ` Julius Schmidt
2019-12-18 12:11 ` Angelo Papenhoff
2019-12-18 15:53 ` Dan Cross
2019-12-18 12:19 ` Paul Ruizendaal
2019-12-19 0:20 ` Paul Ruizendaal
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=AC1798F2-2248-4751-93D2-73C2166D4A44@planet.nl \
--to=pnr@planet.nl \
--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).