On Tue, 18 Mar 1997 21:21:08 +0000 Nishant Deshpande <nd4@DOC.IC.AC.UK>
writes:
>hi all,
>
>can anyone tell me about CBLOCK? i've read what little is given
>in the Microchip help note..
>
>in one of the app notes there's this piece of code
>
>CBLOCK 0x0C
>
>        <lots of variables>
>
>END
>
>
>
>now what does the 0x0C mean?


        It's the address to put the first byte of data at.


        Any subsequent cblocks that do not specify an address will use
the next consecutive address.  I use this a LOT to give a sort of
"encapsulation" by placing variables inside the subroutines that use
them.  It's a little like a static local variable, though they CAN be
accessed from outside (they're really global).  I've used this approach
from my early 6800 programming days instead of putting a tone of ram
allocation at the top of the program, then losing track of it.
        In naming variables inside routines, I include a portion of the
name of the routine in the name, hopefully making the name unique.  For
example, temp inside an A/D routine becomes adTemp, which distinguishes
it from pwmTemp.

Harold