From: Jonathan Gray <jsg@jsg.id.au>
To: Ronald Natalie <ron@ronnatalie.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Any Bell 8-bit UNIX Efforts?
Date: Wed, 1 Mar 2023 13:50:30 +1100 [thread overview]
Message-ID: <Y/69doVggsnRgW9v@largo.jsg.id.au> (raw)
In-Reply-To: <em6a0da8e9-1cd2-4b9c-8e91-c803c257d17a@a42f0ac3.com>
On Wed, Mar 01, 2023 at 02:07:06AM +0000, Ronald Natalie wrote:
> The first chapter of K&R was out as a technical paper at least a year prior
> to the book coming out.
> By the time the book had come out, there had already been some evolution in
> the language. The “Phototypesetter” and soon after “Version 7” versions
> of the compiler were heading toward what would be come ANSI by the time BDS
> came out.
The background to BDS C is described in an interview with Leor Zolman
http://www.znode51.de/articles/int4.htm
"I wrote the first cut of BDS C between January and April, 1979,
specifically in order to compile a C version of the Othello game written
by Robert Halstead at the Real-Time Systems Lab at MIT"
>
> Amusingly, I ended up working for an unrelated company called BDS and ended
> up with the BDS.COM domain. Eventually, we changed the name of the company
> and after brief inquiry from them donated the BDS.COM domain to the compiler
> guys.
>
> At least it didn’t come with a prayer book like the Metalware compiler
> (which really needed all the divine intervention that it could get).
MetaWare High C, used by AIS/AOS on the PC RT
>
> ------ Original Message ------
> > From "Rich Salz" <rich.salz@gmail.com>
> To "Dave Horsfall" <dave@horsfall.org>
> Cc "The Eunuchs Hysterical Society" <tuhs@tuhs.org>
> Date 2/28/2023 8:21:42 PM
> Subject [TUHS] Re: Any Bell 8-bit UNIX Efforts?
>
> > >
> > > I'm glad that you qualified it with "for the time"; I've used it, and
> > > calling it a "C compiler" was a bit of a stretch[*]. Later on I
> > > bought
> > > the Hi-Tech C compiler, and it was full ANSI, with function prototypes
> > > etc.
> >
> > Hmm. K&R publication date was February 1978. BDS C was released in
> > August 1979. So it was certainly C as known at that time. X3J11 was
> > convened in 1983 and published in 1985. Doesn't seem like a good
> > comparison.
> > >
next prev parent reply other threads:[~2023-03-01 2:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 19:48 [TUHS] " segaloco via TUHS
2023-02-27 3:55 ` [TUHS] " Warner Losh
2023-02-27 10:57 ` Jonathan Gray
2023-02-28 18:59 ` segaloco via TUHS
2023-02-28 19:03 ` Larry McVoy
2023-02-28 19:42 ` Clem Cole
2023-02-28 19:57 ` Bakul Shah
2023-02-28 23:31 ` Dave Horsfall
2023-03-01 0:39 ` Larry McVoy
2023-03-01 1:21 ` Rich Salz
2023-03-01 1:27 ` Warner Losh
2023-03-01 2:07 ` Ronald Natalie
2023-03-01 2:35 ` Dan Cross
2023-03-01 2:38 ` Ronald Natalie
2023-03-01 3:02 ` [TUHS] IBM RT/PC compilers [was " Charles H. Sauer
2023-03-01 4:02 ` [TUHS] " George Michaelson
2023-03-01 14:12 ` [TUHS] " Chet Ramey
2023-03-02 9:05 ` Jaap Akkerhuis via TUHS
2023-03-02 19:26 ` Clem Cole
2023-03-01 2:50 ` Jonathan Gray [this message]
2023-03-01 0:31 ` Jonathan Gray
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=Y/69doVggsnRgW9v@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=ron@ronnatalie.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).