> Does the compiler generate assembly output, or a .LST file, that you can
> look at to see what it's doing?  I have yet to see a compiler that
> doesn't, but my experience is admittedly limited.

Dale,

No, can you believe that????  The version I have is a "demo" version, that
limits the size of your programs.  It makes a .rpt file, but it sure has a
limited amount of info in it.  Perhaps there is a command line arg or
something, but the documentation is pretty sparse on this compiler.  Now,
I'm quite sure that someone will come along and point out my ineptitude with
this compiler.  ;-)  Thanks for your help.

Sidebar:

I've switched to trying to use SDCC, I hope *this* compiler works.  ;-D  If
anyone has any advice/comments/criticism on SDCC, please speak up.  I
certainly don't want to waste time learning a compiler that isn't going to
work right.  It's bad enough finding your own bugs, but when the compiler
can't get it right that really bites.  That is precisely why I gave up using
x86 (MASM) assembler a long time ago.  If you don't know the ins and out's
of 86's and their register quirks, you will have a very hard time dealing
with MASM.  You write one thing, it generates code for what you *must*
really have intended to write.  I'll give it credit for one thing though,
you'll definitely learn the HEX op-codes while using MASM.

michael brown

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.