From: Rob Gingell <gingell@computer.org>
To: Clem Cole <clemc@ccc.com>, Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Looking back to 1981 - what pascal was popular on what unix?
Date: Sun, 6 Feb 2022 19:04:01 -0800 [thread overview]
Message-ID: <df258395-6760-5797-3447-655bbd0f1d41@computer.org> (raw)
In-Reply-To: <CAC20D2Nh0t9dxVbRvXFxXkCfEaWkmp9MP1Xf+=YC3rfXf3SK3g@mail.gmail.com>
On 1/29/2022 11:59 AM, Clem Cole wrote:
> Sun later brought the UCB PI and PC to the SunOS, but pls Rob G/Larry
> correct me here - I think they later did their own compiler when they
> did their new C and Fortran.
Sun never replaced the UCB Pascal front-end, just moved it across
back-ends as it evolved them.
The development of SPARC required Sun to develop back-end expertise.
Although the investments focused on SPARC, there was also work on the
back-ends for the Motorola- and Intel-based products.
Sun's front-end investments began with the SVR4 project as an ANSI C
compiler was needed. (A priority for SVR4 was conformance with
then-current external standards such as POSIX and ANSI. Over the course
of SVR4's development strict ANSI conformance came to be seen as
problematic: most SV licensees didn't just use the release as delivered
and instead merged portions into their extant, and not ANSI, product
source code bases. This led to some late-in-the-project de-ANSIfying of
the source in the interest of making SVR4 more digestible by the licensees.)
That C compiler was the basis for the unbundled C compiler product that
came out at the time of SunOS 4.1.
Sun's larger investments in front-end development were motivated by the
later transition from F77 to F9X. Which is another data point in support
of Clem's frequent observation that FORTRAN is a big deal in parts of
the real world. At that point Sun tended to its own front ends for C,
C++, and FORTRAN but Pascal was always the UCB front end.
prev parent reply other threads:[~2022-02-07 3:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 23:07 Will Senn
2022-01-28 23:18 ` Dan Cross
2022-01-28 23:31 ` Will Senn
2022-01-29 0:03 ` Rob Pike
2022-01-29 0:40 ` Will Senn
2022-01-29 19:05 ` John Cowan
2022-01-29 19:36 ` arnold
2022-01-29 19:59 ` Clem Cole
2022-01-29 20:02 ` Jon Steinhart
2022-01-29 20:13 ` Bakul Shah
2022-01-29 20:30 ` Clem Cole
2022-01-29 20:34 ` Larry McVoy
2022-01-29 21:03 ` Al Kossow
2022-01-29 21:38 ` Larry McVoy
2022-01-29 22:06 ` Bakul Shah
2022-01-29 22:48 ` GREEN
2022-01-30 3:27 ` Larry McVoy
2022-01-30 16:57 ` David Barto
2022-01-30 18:07 ` [TUHS] Compilation "vs" byte-code interpretation, was " Dan Stromberg
2022-01-30 20:09 ` David Barto
2022-01-31 7:59 ` WEB
2022-01-30 22:51 ` Dan Cross
2022-01-30 23:57 ` Dan Stromberg
2022-01-31 0:23 ` Nemo Nusquam
2022-01-31 0:45 ` Steve Nickolas
2022-01-31 17:16 ` Paul Winalski
2022-01-31 20:00 ` Erik E. Fair
2022-01-31 22:45 ` Steve Nickolas
2022-02-02 4:53 ` Adam Thornton
2022-01-31 1:41 ` Phil Budne
2022-02-07 3:04 ` Rob Gingell [this message]
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=df258395-6760-5797-3447-655bbd0f1d41@computer.org \
--to=gingell@computer.org \
--cc=clemc@ccc.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@gmail.com \
/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).