I'll give it a try tonight and let you know.
It's a very different syntax, ¿ where did you got that info ?, I'm curious.
Cheers,
Olgierd
On 18-04-2011 16:57, Rob Connolly wrote:
> __code __at __CONFIG1L _C1L = 0x20;
> __code __at __CONFIG1H _C1H = 0x04;
> __code __at __CONFIG2L _C2L = 0x04& 0
This is nothing magic but simply a variable definition, in the code address
space (__code) at the correct address (__at adr) and initialized with a
value!
The name is not important, e.g.
char foovalue; /*variable*/
char foovalue = 42; /* initialized*/
__code char foovalue = 42; /*address space
Yeah, but why sometimes we use "__code" and others simply "code" and
"CONFIG" or "__CONFIG", general concept and syntax it's in fact the
same, keywords or macros are the difference (at least it seems so to me).
Regards
Olgierd
On 19-04-2011 7:47, Sébastien Lorquet wrote:
This is nothing magi
"code", "data" and "at" are obsolete and shall be replaced by "__code"
"__data" and "__at".
in the past you could not have a variable named "data" because it was a
reserved word.
__CONFIG1L and other are addresses defined in the PIC headers.
CONFIG seems to be a macro that expands to what I wrot
