The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: david@kdbarto.org (David)
Subject: [TUHS] Algol68 vs. C at Bell Labs / Pascal
Date: Thu, 30 Jun 2016 15:55:17 -0700	[thread overview]
Message-ID: <47BC1783-6192-4C1B-8CBA-249ABF736ADB@kdbarto.org> (raw)
In-Reply-To: <mailman.27.1467307673.30583.tuhs@minnie.tuhs.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]


> On Jun 30, 2016, at 10:27 AM, schily at schily.net (Joerg Schilling)
> Marc Rochkind <rochkind at basepath.com> wrote:
> 
>> Bill Cheswick: "What a different world it would be if IBM had selected the
>> M68000 and UCSD Pascal.  Both seemed
>> to me to better better choices at the time."
>> 
>> Not for those of us trying to write serious software. The IBM PC came out
>> in August, 1981, and I left Bell Labs to write software for it full time
>> about 5 months later. At the time, it seemed to me to represent the future,
>> and that turned out to be a correct guess.
> 
> I worked on a "Microengine" in 1979.
> 
> The Microengine was a micro PDP-11 with a modified micro code ROM that directly 
> supported to execute p-code.
> 
> The machine was running a UCSD pascal based OS and was really fast and powerful.
> 
> Jörg

Very likely one of the Western Digital products. They were the first to take UCSD Pascal and burned the p-code interpreter into the ROM. Made for a blindingly fast system. I worked with the folks who did the port and make it all play together. Fun days.

I worked on the OS and various utility programs those days. Nothing to do with the interpreters.

When the 68000 came out SofTech did a port of the system to it. Worked very well; you could take code compiled on the 6502 system write it to a floppy, take the floppy to the 68k system and just execute the binary. It worked amazingly well.

	David



       reply	other threads:[~2016-06-30 22:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.27.1467307673.30583.tuhs@minnie.tuhs.org>
2016-06-30 22:55 ` David [this message]
     [not found] <mailman.25.1467300770.30583.tuhs@minnie.tuhs.org>
2016-06-30 23:00 ` David
2016-06-30 23:43   ` William Cheswick

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=47BC1783-6192-4C1B-8CBA-249ABF736ADB@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).