The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Henry Bent <henry.r.bent@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] DEC compilers (was Happy birthday, John Backus!)
Date: Wed, 5 Dec 2018 13:26:09 -0500	[thread overview]
Message-ID: <CAEdTPBcbh241896vNTgsBGU20g6a_MDQ1ikJQf+bAx_DNOAyoQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Nh5w7wPMo0s568cToPSBJd7gtcEWdif57wizqV09_CJg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]

On Wed, 5 Dec 2018 at 13:01, Clem Cole <clemc@ccc.com> wrote:

> I'm not sure which languages did eventually get supported and on which
> versions of Ultrix.  But once Paul's lk was released (and you can still
> find it in /bin on the base Ultrix distributions), you did indeed see a
> number of the languages move to Ultrix.  I think for the Vax it was just
> VAX/11C, Fortran and Pascal.  I think Ultrix11 may have gotten Fortran, but
> as I said; I don't remember.  I do remember the TIG folks talking about a
> PL/1 project and a proposal for Cobol and RP/G because some of the Wall
> Street types wanted them, but I don't remember any of those getting
> released (that said, I was also not watching things Vaxen by that time).
>  By the time I came back to Ultrix to do the MIPS 4000 stuff a few years
> later, tech languages offerings were different and the GEM compilers had
> come on the scene.
>

http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/4.0_Jun90/AA-MG63B-TE_ULTRIX_Technical_Summary_Jun90.pdf
seems to imply that as of Ultrix 4.0, there were COBOL and Ada compilers
for the VAX (Table 4-1).  Elsewhere VAX LISP for Ultrix is mentioned, which
I had no idea existed.  I hope that these compilers have been preserved
somewhere, as I imagine they sold in relatively small quantities.

-Henry

[-- Attachment #2: Type: text/html, Size: 1825 bytes --]

  parent reply	other threads:[~2018-12-05 18:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 16:24 Paul Winalski
2018-12-05 16:46 ` Paul Winalski
2018-12-05 17:06   ` Warner Losh
2018-12-05 17:58   ` Clem Cole
2018-12-05 18:16     ` Paul Winalski
2018-12-05 18:26     ` Henry Bent [this message]
2018-12-05 18:46       ` Clem Cole
2018-12-05 18:56         ` Lars Brinkhoff
2018-12-05 19:15         ` Paul Winalski
2018-12-05 21:35           ` Arrigo Triulzi
2018-12-07 19:03             ` Paul Winalski
2018-12-05 19:13 Norman Wilson

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=CAEdTPBcbh241896vNTgsBGU20g6a_MDQ1ikJQf+bAx_DNOAyoQ@mail.gmail.com \
    --to=henry.r.bent@gmail.com \
    --cc=tuhs@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).