Clyde Smith-Stubbs wrote:

> Roger,
>
> > I find it easier to debug the compiled code, if I only have to refer to one
> > list file.  The other compilers that I use produce a single list file, so I
> > assumed that this was the norm.
>
> I think you'll find the other compilers don't have a linker, they just
> compile a single source file.
>
> Regards, Clyde

Interesting enough, the 2 low end compilers I have, both have a linker with an
option for producing one list file, while the higher end compiler's I have, such
as HiTech's  and Taskings, don't.  Also, the low end compilers, have options to
produce more readable listings by including the original source code (before the
pre-processor) in the listing, while the higher end compilers don't.  I'm
assuming that the low end products were designed for people who needed an easier
to read listing for the same reason they needed a cheaper compiler.  They were
new to embedded C and C in general and needed the "learner" grade compiler to
help them along.  Also, they could not justify spending the extra money for a
"production" grade compiler.  At least that was the case with me :)  Anway, I
kinda miss the easier to read listing files (without the macro source code
stripped out).  Even with the longer larger file files size (some of the combine
d
listings are over 1 Meg), it's easier to search one file, than across several
list files.  I'm sure as my experience with compilers increases I won't need
them.  It would be a nice option to have in any case.

Roger Morella