The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Early Internet work (Was: History of select(2))
Date: Sun, 29 Jan 2017 18:30:37 -0800	[thread overview]
Message-ID: <20170130023037.GQ15819@mcvoy.com> (raw)
In-Reply-To: <CAC20D2PsrxDUbV8G-hELqLvn2e-9faPg+FAZ1DDkbDm6KrPU9A@mail.gmail.com>

On Sun, Jan 29, 2017 at 09:19:48PM -0500, Clem Cole wrote:
> That said, is you want a goos starting point the best C compiler for the
> 8080 was the Leor Zolman's "Brain Damaged Software" C -- aka BDS C.   Which
> he has put in the public Domain:   http://www.bdsoft.com/resources/bdsc.html

Oh, how I know that compiler.  Or knew it.  When I was a student and they 
had 30-40 people logged into the VAX 11/780, I said "screw this, it's too
slow" and I got $2000 Okidata CPM Z80 machine (why that one?  Because it
had an integrated printer and the screen had colors, wasn't B&W). 

CPM wasn't that great, I was used to BSD Unix, so I wrote a bunch of clones
of the unix commands like ls, cat, more, cp, rm, etc.  For those I used
assembler because I was trying like crazy to get each one to fit in one
sector of the floppy disk; that was faster to load and left more room on
the disk for other stuff.

Anyhoo, that BDS compiler was awesome.  Not as awesome as turbo pascal but
it wasn't pascal, if you know what I mean.

I did most of my school projects on that machine, wrote my on dial / terminal
program (why?  Because I could :), all of that in BDS C.

Anyone remember his non-standard standard I/O?


  reply	other threads:[~2017-01-30  2:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 17:41 Noel Chiappa
2017-01-29 20:28 ` Paul Ruizendaal
2017-01-30  1:34 ` Nick Downing
2017-01-30  2:19   ` Clem Cole
2017-01-30  2:30     ` Larry McVoy [this message]
2017-01-30  2:43       ` Ron Natalie
2017-01-30  2:43       ` Clem Cole
2017-01-30  2:32     ` Larry McVoy
2017-01-30  2:39       ` Clem Cole
2017-01-30 13:13     ` Dave Horsfall
2017-01-30 13:37       ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2017-01-30 16:15 Noel Chiappa
2017-01-30 16:41 ` Clem Cole
2017-01-30 16:44 ` Clem Cole
2017-01-30 15:34 Noel Chiappa
2017-01-30 21:20 ` Paul Ruizendaal
2017-01-30  2:50 Noel Chiappa
2017-01-30  3:33 ` Nick Downing
2017-01-30  3:38   ` Ron Natalie
2017-02-08  3:58   ` Dave Horsfall
2017-01-30  8:26 ` Paul Ruizendaal
2017-01-30  1:44 Noel Chiappa
2017-01-29 18:35 Noel Chiappa
2017-01-16 15:17 Noel Chiappa
2017-01-16 14:42 Noel Chiappa
     [not found] <mailman.1.1484532001.2693.tuhs@minnie.tuhs.org>
2017-01-16 10:21 ` Johnny Billquist
2017-01-16  1:47 Noel Chiappa
2017-01-16 10:06 ` Paul Ruizendaal
2017-01-16  1:01 Noel Chiappa
2017-01-16 10:31 ` Paul Ruizendaal
2017-01-16 12:07 ` Tony Finch
2017-01-15  2:30 Noel Chiappa
2017-01-13 13:19 Noel Chiappa
2017-01-09  2:35 [TUHS] History of select(2) Warren Toomey
2017-01-09 10:36 ` Paul Ruizendaal
2017-01-12  3:54   ` Clem Cole
2017-01-13  9:13     ` Paul Ruizendaal
     [not found]       ` <20170114164102.GA31665@yeono.kjorling.se>
2017-01-16  0:13         ` [TUHS] Early Internet work (Was: History of select(2)) Paul Ruizendaal

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=20170130023037.GQ15819@mcvoy.com \
    --to=lm@mcvoy.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).