> No, havent tryed that, whats the diference betwen
>
> Cons unsigned char      str1 = "String number 1";
> const rom char * str3 = "String number 3";
>
> Isn't suposed that werever you put const the dta will be stored on the
> ROM? Or I'm confusing compilers?

AFAIK a const qualifier has some consequences in the area of
assignability, but a compiler is not required to put the data in a
certain area. The probelm with PICs is that ROM and RAM are separate
address spaces, so a 'generalised' pointer (that can point to both
areas) would require more complex code when it is used. For the C18
compiler uChip instead choose to introduce the 'rom' qualifier to force
stoting in ROM. A consequence is that a declaration with 'rom' behaves
(internally) quite different from one without. Note that using a 'rom'
pointer looks the same as using a RAM pointer, but the generated code is
very different.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body