From: david@kdbarto.org (David)
Subject: [TUHS] Algol68 vs. C at Bell Labs / Pascal
Date: Thu, 30 Jun 2016 16:00:22 -0700 [thread overview]
Message-ID: <C59B0097-EA50-42F7-B535-97F2FF6A11DE@kdbarto.org> (raw)
In-Reply-To: <mailman.25.1467300770.30583.tuhs@minnie.tuhs.org>
> Ronald Natalie <ron at ronnatalie.com>
>
>>
>> On the other hand, there was
>> no excuse for a Pascal compiler to be either large, buggy, or slow, even before Turbo Pascal.
>>
> I remember the Pascal computer on my Apple II used to have to use some of the video memory while it was running.
UCSD Pascal, the Apple Pascal base, would grab the video memory as space to write the heap when compiling. When the Terak system was in use at UCSD the video memory would display on the screen so you could watch the heap grow down the screen while the stack crawled up when compiling. If it ever hit in the middle, you had a crash. Exciting times.
Terak systems were 11/03 based, IIRC. (http://www.threedee.com/jcm/terak/)
David
next parent reply other threads:[~2016-06-30 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.25.1467300770.30583.tuhs@minnie.tuhs.org>
2016-06-30 23:00 ` David [this message]
2016-06-30 23:43 ` William Cheswick
[not found] <mailman.27.1467307673.30583.tuhs@minnie.tuhs.org>
2016-06-30 22:55 ` David
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=C59B0097-EA50-42F7-B535-97F2FF6A11DE@kdbarto.org \
--to=david@kdbarto.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).