John J. McDonough wrote :

> With two code directives, one of them needs to have a name...

Hm, I thought that MPASM/MPLINK would supply some
made-up names for any un-named CODE segment, not ?

Now, I think you should *always* put your own name
on all CODE directives anyway, since that make the MAP files
much easier to read...

And personaly, I prefer to put a CODE directive for all/most
subroutines in the code. That makes it easy to read the
individual sizes for each segment from the MAP file. And
if you find out that you have to pin someting (like a table)
at a fixed address, the rest of the code will neatly spread
around it without any other changes.

Best Regards,
Jan-Erik.




-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist