> > And a related thing, when building a project
> > using the environment as-is, the .lst files
> > are filled up with .INC file listnings.
> > I have removed a lot of this by putting
> > NOLIST/LIST in e.g. STD.INC and STD_DEF.INC
> > in the \src\pic directory (and in my application
> > specific copy of QQQ.INS.ASPIC).
> >
> > Now, do you have any general method to handle
> > the growing lst files ?
>
> Yeah, ignore them.  The LST files are pretty useless except for debugging
> macros or checking the results of assembly time computations.

This is what i have ended up doing as well. If I get an error then I search
the the LST file for an open square bracket ("[") which encloses the message
number. However if you do this you will find out how often Olin does not put
,w or ,f on operands (The FIFO macros are prime ones here) :)))))


> > I'm using this project for a new
> > section in my PDF document called
> > "Creating a new project" (under the
> > new chapter "Tips-n-Tricks). It's not
> > online yet, but i you'd like to review
> > the new section, I could mail you a copy
> > directly.


Consider the above a tip you may like to include.

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body