Wouter van Ooijen wrote:

>> Second, the config is all saved in the mplab project.  In the configure
>> menu, and the config bits part.  I prefer to use this than specify it
>> in the code, because it's much clearer.
> 
> Bad idea IMHO, the source should specify everthing. But if you want it
> this way you should include the project file(s) to we can check.

Another reason (of the many) why this might be a bad idea is: Are you
really sure it is saved in the MPLAB _project_ file? MPLAB uses project
files and workspace files (and its global configuration), and it's not
really very obvious which configuration item gets stored where. It would
make sense to store the processor configuration bits in the project file,
but then, it would make sense to store the processor type in the project
file, too -- but that one is stored in the workspace file, and the
workspace file is binary, so it's not really easy to find out what's in
there. 

So, unless you are intimately familiar with the way MPLAB works, you may
not want to rely on guesses where what gets stored. Besides, it's such a
good feeling to load a project from years ago and it just works, without
having to fiddle with the MPLAB configurations, and without having to try
to find out how that had to be set for this project to work... :)

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