Jeff Swayze wrote...

[...]

>My question is: Is there a defacto standard or any kind of guideline as to
>how to manage the variables and equates associated with an include file?

[...]

I used to code by the method you described, with multiple source
files that I'd incorporate into a project by inserting them into
the code flow of a "main" file by using the #include directive.

There is a much, MUCH better way of organizing code, and that is
to use relocatable code and let MPLINK build the project.  An
added benefit of doing this is that it gives you scope control
over the symbols (i.e., variables and code labels) in a file,
allowing you to make them visible in other modules or not, at
will.

I found learning to use the linker rather non-trivial, but
finally got the hang of it (at least for my limited needs).  I
put up a small example of how to use it, at:

http://mywebpages.comcast.net/dilatush/lnkdemo2.zip

This is an MPLAB 5.x project, and will take a small bit of
fiddling to turn it into an MPLAB 6.x project; maybe the
converter utility can take care of that for you.

Hope this helps...

Dave D.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads