The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: [TUHS] Re: History of non-Bell C compilers?
Date: Sat, 09 Mar 2024 18:13:33 -0800	[thread overview]
Message-ID: <m1rj8gw-003DQEC@more.local> (raw)
In-Reply-To: <CAOkr1zVewrFznWXHopfKLx+kj+6SeNPC1Lxq_0=dpiJvstpqXw@mail.gmail.com>

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

At Thu, 7 Mar 2024 17:24:11 -0700, Marc Rochkind <mrochkind@gmail.com> wrote:
Subject: [TUHS] Re: History of non-Bell C compilers?
>
> Then I got an IBM PC in 1982, with an 8088 (16-bit word, 8-bit bus), and
> I'm pretty sure the first real C compiler was Lattice C. Microsoft picked
> it up and called it Microsoft C. Then, maybe a couple of years later, they
> came out with their own C compiler, written in-house, I think. (As I
> recall, I got my Lattice C compiler, which was very expensive, for free for
> writing a review for BYTE Magazine, but I can't find the review in my
> office or online, so maybe I'm imagining that. Or maybe I never finished
> the review or they didn't print it.)

Oh, Lattice C!  The one compiler I came to hate.  It was rather buggy
and had many incompatibilities and difficulties if one was already
accustomed to using writing C on Unix.  Microsoft C in its early days
post-Lattice was somewhat less buggy, but still a bane to use, even on
Xenix where the libraries were more "complete".

I don't think the Mark Williams C compiler has been mentioned in this
thread yet.  It was of course the same one created for and used in their
Coherent system, but it was also released for various systems including
MS-DOS it was a pure joy to use.  It was extremely compatible with Unix
C of the day (having been created to build a Unix clone, and on a PDP-11
no less), and equally reliable, and came with many additional
command-line tools that were similarly familiar.

I wrote more about my experiences with some non-Unix compilers back a
few years ago in a tangentially related thread:

      https://www.tuhs.org/pipermail/tuhs/2020-May/021231.html

--
					Greg A. Woods <gwoods@acm.org>

Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>

[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2024-03-10  2:13 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 23:14 [TUHS] " Tom Lyon
2024-03-07 23:24 ` [TUHS] " Warner Losh
2024-03-07 23:39   ` Dave Horsfall
2024-03-07 23:49     ` Larry McVoy
2024-03-07 23:56       ` Luther Johnson
2024-03-08 14:03         ` John Foust via TUHS
2024-03-07 23:59       ` Greg 'groggy' Lehey
2024-03-08  0:08         ` Rich Salz
2024-03-08  0:30           ` Warner Losh
2024-03-08  0:57             ` Rob Pike
2024-03-08  1:08               ` Bakul Shah via TUHS
2024-03-08  1:10                 ` Rob Pike
2024-03-08  1:12                   ` Rob Pike
2024-03-08  1:22                     ` Bakul Shah via TUHS
2024-03-08  9:33               ` arnold
2024-03-08  9:45                 ` Wesley Parish
2024-03-08 13:06                   ` Luther Johnson
2024-03-08 18:33               ` William H. Mitchell
2024-03-10  3:14                 ` Adam Thornton
2024-03-11 22:21       ` Phil Budne
2024-03-07 23:52   ` Warner Losh
2024-03-08  0:15     ` Charles H Sauer (he/him)
2024-03-08  0:30       ` Marc Rochkind
2024-03-08  0:54         ` Heinz Lycklama
2024-03-08  1:48           ` segaloco via TUHS
2024-03-08  2:12             ` Tom Lyon
2024-03-08  2:13     ` Lawrence Stewart
2024-03-08  3:15     ` Jonathan Gray
2024-03-07 23:24 ` Luther Johnson
2024-03-07 23:27   ` Luther Johnson
2024-03-07 23:44     ` Tom Lyon
2024-03-08  0:24       ` Marc Rochkind
2024-03-08  1:27         ` Jeffry R. Abramson
2024-03-10  2:13         ` Greg A. Woods [this message]
2024-03-08  2:26 ` Will Senn
2024-03-08  3:03   ` Peter Yardley
2024-03-08  3:28 ` George Michaelson
2024-03-08  3:58   ` Luther Johnson
2024-03-08  5:53 ` Lars Brinkhoff
2024-03-08 13:42 ` Henry Bent
2024-03-08 14:00   ` arnold
2024-03-08 14:16   ` Warner Losh
2024-03-08 15:44 ` Paul Winalski
2024-03-08 17:18   ` Adam Thornton
2024-03-10  2:31 ` Damian Wildie
2024-03-11 17:12 Paul Ruizendaal
2024-03-11 20:44 ` Marc Rochkind
2024-03-11 22:28   ` Peter Yardley
2024-03-12  0:30     ` ron minnich
2024-03-12 13:31       ` Larry Stewart
2024-03-12 16:41     ` Paul Winalski
2024-03-12 14:55   ` Henry Bent
2024-03-12 17:17     ` Marc Rochkind
2024-03-13 14:37       ` Clem Cole
2024-03-13 15:28         ` Marc Rochkind
2024-03-13 15:33           ` Warner Losh
2024-03-13 15:53           ` Clem Cole
2024-03-12 15:42 ` Paul Ruizendaal
2024-03-12 23:08 Steve Simon
     [not found] <aee297f1-2f6a-4620-87f7-f1672ae03b61@osta.com>
2024-03-15  3:34 ` Heinz Lycklama

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=m1rj8gw-003DQEC@more.local \
    --to=woods@robohack.ca \
    --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).