The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Zilog Z80 Unix
Date: Mon, 24 Apr 2017 10:04:49 +1000	[thread overview]
Message-ID: <20170424000449.GD99987@eureka.lemis.com> (raw)
In-Reply-To: <20170423001300.GK15459@mcvoy.com>

On Saturday, 22 April 2017 at 17:13:00 -0700, Larry McVoy wrote:
> On Sun, Apr 23, 2017 at 07:07:13AM +1000, Dave Horsfall wrote:
>> I remember BDS C for all the wrong reasons; I can only repeat a remark
>> from Henry Spencer about another alleged C compiler: "To be called a C
>> compiler, it ought to at least be able to compile C."  My Z-80 C compiler
>> was Hi-Tech C, which was full ANSI.
>
> I've never heard of Hi-Tech C but I am apparently more forgiving.  I
> spent many happy hours using BDS C.  It wasn't exactly standard, the
> standard I/O library was far from compat, but whatever, it was a C
> compiler on a CP/M system.  Pretty pleasant.

Yes, I think this is a reasonable viewpoint.  It was my first ever C
environment, and I really recognized how non-standard it was when I
got a standard C compiler and had to rethink (and rewrite).

Am I correct in remembering that this was the compiler that Craig
Finseth used for MINCE, my first exposure to (also non-standard)
Emacs?

Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170424/19e4b5e4/attachment.sig>


  reply	other threads:[~2017-04-24  0:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20  1:42 Erik E. Fair
2017-04-20  2:54 ` Jason Stevens
2017-04-20  3:09 ` Bakul Shah
2017-04-20  3:40   ` Gregg Levine
2017-04-20  4:34     ` Bakul Shah
2017-04-20  4:50       ` Warner Losh
2017-04-20  7:03       ` Wesley Parish
2017-04-20  7:32         ` Wesley Parish
2017-04-20  4:32   ` Rik Schneider
2017-04-20 13:05 ` Clem Cole
2017-04-22 21:07   ` Dave Horsfall
2017-04-22 23:59     ` Clem cole
2017-04-23  0:01     ` Clem cole
2017-04-23  0:13     ` Larry McVoy
2017-04-24  0:04       ` Greg 'groggy' Lehey [this message]
2017-04-24  0:40         ` Larry McVoy
2017-04-23  5:14   ` Wesley Parish
2017-04-23  5:14   ` Wesley Parish
2017-04-20 21:32 ` Dave Horsfall
2017-04-20 21:59   ` Larry McVoy
2017-04-20 22:33     ` Steve Nickolas
2017-04-20 23:28     ` Pete Turnbull
2017-04-20 23:19   ` Harald Arnesen
2017-04-21  0:03     ` Andy Kosela
2017-04-23 17:58 ` Michael Welle
2017-04-20 12:34 Noel Chiappa
2017-04-20 13:41 ` Mutiny 

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=20170424000449.GD99987@eureka.lemis.com \
    --to=grog@lemis.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).