Jan-Erik Soderholm wrote:
>> If I would this would not convince me: always CBLOCK would have
>> prevented that error too. Hardcoding is the evil here, not CBLOCK.
>
> I'm not sure I understand here.
> Two CBLOCK's can overlap, not ?

Yes they can, since CBLOCK is for defining enumerated constants and has
nothing to do with RAM addresses.  CBLOCK is almost hard coding.  You can
still hard code the addresses of variabled defined with RES, but at least
that way the linker catches it if you overlapped other variables or went
outside the valid address range.


********************************************************************
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