From: Larry McVoy <lm@mcvoy.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Any Bell 8-bit UNIX Efforts?
Date: Tue, 28 Feb 2023 16:39:16 -0800 [thread overview]
Message-ID: <20230301003916.GA15064@mcvoy.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2303011025390.4881@aneurin.horsfall.org>
On Wed, Mar 01, 2023 at 10:31:59AM +1100, Dave Horsfall wrote:
> On Tue, 28 Feb 2023, Clem Cole wrote:
>
> [...]
>
> > A bit later, Loer Zohlman wrote??BDS C,??which was pretty darned
> > good/fairly complete C implementation for the time; [...]
>
> 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.
BDS C wasn't ANSI by any stretch but it was small, fast, and available
when everything else was slow (except Turbo Pascal, crazy fast, but,
um, Pascal. 'Nuf said).
While I had to relearn the stdio lib for real C, I did not find it
hard at all to switch back and forth and I wrote a ton of useful
stuff in BDS C. Super grateful to have had it.
next prev parent reply other threads:[~2023-03-01 0:39 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 [this message]
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
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=20230301003916.GA15064@mcvoy.com \
--to=lm@mcvoy.com \
--cc=dave@horsfall.org \
--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).