And I say all this with a :) looking for good info.
>  Just specify a different section explicitly.
>
>   
In Microchip literature and other places there are numerous ways 
suggested, including:
1: Specify a different section
2: Place the arrays in different files
3: Modify the linker file.

And I'm not anywhere near an expert, but have tried them all (most) with 
little success. It may be some little detail that I don't have correct, 
but Not one of the examples follows through the whole method with code 
examples, I'll fault Microchip with poor examples. Here are some of the 
issues:
1: They sometimes add a "NAME" declaration in the linker, and then use 
that in the "C" file. Not sure where to safely assign an address to put 
the variable. I think I could check the MAP file, but how do I know with 
some small changes to the program, that's still safe.
2: The "extern int a_well[10];" , should it be with [ ] since the size 
is defined in the file. Can/must this line be at the beginning of the 
"C" file with other external declarations, or in main() or other function.
3: My linker file doesn't have  many gpr? areas, if I reduce the gpr0, 
what are the rules?

Microchip specs claim that the 1320 has 256 data, the C18 package claims 
to somewhat handle the near/far bit, but the whole package is cumbersome.

Looking for a good current reference on "C" most of my stuff is older 
including K & R copyright 1978 is the oldest.

> That doesn't mean the extra bytes are all in the same bank.  I never use the memory gauge.  Look in the MAP file to get the real info.
>   
They give you a nice looking tool, no info on the usage, and then 
doesn't give good info. Ideally, it would use different colors and 
differentiate between the banks.

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