> Only if I used those dumb include files... Which I don't,

But then you have to reproduce all the information in them in some other
form, or at least the part that you use.  The include files aren't
elegant, but they do eliminate the chance of you making a little mistake
that takes a long time to find.

I would leave the symbols in those include files alone and create new ones
that expand to the register and the bit within the register.  That also
makes your code more standard in that RP0, for example, means what
everyone else will assume it means.  For example, you could

#define STATUS_RP0 STATUS,RP0

This still takes the RP0 bit number definition from the Microchip file so
that you can't accidentally get it wrong, but still gives you the combined
symbol you want.

> as you know,

Well I didn't.  Sorry, I don't keep track of everyone's individual quirks.

> mostly because they don't define bits with #define.

Again, this would best be done in addition to, not instead of, the
Microchip include file.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu