From: Toby Thain <toby@telegraphics.com.au>
To: "A. P. Garcia" <a.phillip.garcia@gmail.com>,
Warner Losh <imp@bsdimp.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Isaacson v Unix [really RMS bashing]
Date: Mon, 7 Jan 2019 00:05:27 -0500 [thread overview]
Message-ID: <492f4b7d-82a9-5ea7-0aa7-7303cc72b254@telegraphics.com.au> (raw)
In-Reply-To: <CAFCBnZt-8i79HOKka1y4oNy70v83e3=9LfjJcLAS+BY0VfJ5Fw@mail.gmail.com>
On 2019-01-06 9:59 PM, A. P. Garcia wrote:
>
>
> On Sun, Jan 6, 2019, 9:39 PM Warner Losh <imp@bsdimp.com
> <mailto:imp@bsdimp.com> wrote:
>
>
>
> On Sun, Jan 6, 2019, 7:06 PM Steve Nickolas <usotsuki@buric.co
> <mailto:usotsuki@buric.co> wrote:
>
> On Sun, 6 Jan 2019, A. P. Garcia wrote:
>
> If not for GNU, Unix would still have been cloned. Net/2
> happened in
> parallel, did it not?
>
>
> Berkeley actively rewrote most of unix yes. Net/1 was released about
> the same time GNU was getting started. Net/2 and later 4.4 BSD
> continued this trend, where 4.4 was finally a complete system.
> BSD386 only lagged Linux by about a year and had much stronger
> networking support, but supported fewer obscure devices than linux...
>
> Warner
>
> Ps I know this glosses over a lot, and isn't intended to be pedantic
> as to who got where first. Only they were about the same time... and
> I'm especially glossing over the AT&T suits, etc.
>
>
> It's really hard to say. How would you compile it? Clang didn't come
> along until 2007. The Amsterdam Compiler Kit, perhaps?
>
If you're asking about non-gcc ANSI C compilers? There were dozens;
sometimes several per platform. One random example was lcc* (1994). And
of course the vendor compilers at which gcc specifically took aim.
There were also quite a number of non-GNU C++ compilers.
--Toby
* - https://en.wikipedia.org/wiki/LCC_(compiler)
next prev parent reply other threads:[~2019-01-07 5:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 23:41 Jon Steinhart
2019-01-07 1:29 ` A. P. Garcia
2019-01-07 1:59 ` Steve Nickolas
2019-01-07 2:39 ` Warner Losh
2019-01-07 2:59 ` A. P. Garcia
2019-01-07 3:32 ` Warner Losh
2019-01-07 5:05 ` Toby Thain [this message]
2019-01-07 5:36 ` Andy Kosela
2019-01-07 1:38 ` Toby Thain
2019-01-07 2:11 ` Larry McVoy
2019-01-07 2:31 ` A. P. Garcia
2019-01-07 0:49 Larry McVoy
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=492f4b7d-82a9-5ea7-0aa7-7303cc72b254@telegraphics.com.au \
--to=toby@telegraphics.com.au \
--cc=a.phillip.garcia@gmail.com \
--cc=imp@bsdimp.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).