Wouter van Ooijen wrote:
> Not if used properly: only one CBLOCK with a start value, most
> convenient place is in the processor header file. in the main code
> file (and included code sub-files) only CBLOCKs without start value.
>
> No overlaps this way, but still no check on the upper bound.

But then only if you use CBLOCK exclusively for creating variables.  One set
of enumerated constants, which is what CBLOCK is really for, and this scheme
breaks.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist