..just make sure you don't include that header in the same file where you define the array. Otherwise you'll get compiler complaints about duplicate definitions or some such. I've seen code that uses #ifdefs and #undefs and such as hacks around this.

You might want to specify what space the array lives in. I think th straight instantiation will put the array on the heap, which (again I think) ends up in the internal RAM. That memory is obviously limited, so if you do:

byte xdata TEST[] = { (byte) 0x01 ... };

the compiler will put the array into the external data memory, if your hardware supports this. (Dunno what'll happen if you don't have hardware support for xdata.)

(Guess who was just bitten by this????)

Also, if the array is meant to be constant, save some more space by putting it into code space:

byte code TEST[] { (byte) 0x01, ...};

This all assumes the Keil tools.

--a