From: Richard Erlacher <richard(a)idcomm.com>
From: Richard
Erlacher <richard(a)idcomm.com>
Use the editor that comes with the mailer, please.
What???
Unless your system is severely crippled your Email has an
editor that will allow your to strip the excess non relevent text.
Try it, make it easier to read on the other end.
> I havent a clue why you said that at all since the
origin of the
smallc-c
> compiler is 8080? I still have the original DDJ
articles with
sources.
What I
said (I thought) was that I don't want to fiddle with small-C to
the
extent of writing a new code generator for the
'HC11, 'HC05's,
805x-series,
PIC, etc, since Hi-Tech already has a code generator
for their compiler
for
No problem with that. But I thought the initial problem was testing a
bunch
of ISBC8020s? Where did all the other excess about other cpus come
into that?
each of those. It would be a BIG job to do that for
the Hendrix
compiler,
reduced though it is, since what's needed is a
general enough compiler
that
once I write a debug monitor based on some existing
model I already have
and
I wouldn't know, I did did the later version for Z80 with TDL opcodes.
know. It's not enough that the 8080 and Z80 are
already supported,
since
Also 8088 and maybe later.
I'll only need to use the 8080, which, BTW,
it's not obvious that the
Hi-Tech 'C' supports. As I said, if I'm going to wander into the
quagmire,
I avoid the quagmire and use asm.
the near future. I'm quite sure nobody is going to
hire me to generate
code
for the Z80 or 8080. I've been known to write code
in assembler as
well,
but haven't done anything for hire in about 10
years that has required
Z80
or 8080 coding.
While I understand the desire it's all outside the scope of the original
problem to test and apparently use a bunch of 8085 multibus cards.
Oh, z80 is still out there as Z180, Z380 and Rabbit for embedded
apps and CPU library cores in gate arrays.
Allison