??? 09/24/08 09:23 Read: times |
#158572 - It didn't actually compile with CONST Responding to: ???'s previous message |
It's quite interesting,
I have it declared as CODE only, when I declare it as COSNT + CODE as suggested I can an error. *** ERROR C204 IN LINE 330 OF cpanel.c : pointer: const to non-const assignment The RC51 error description is (Pg 123) "A const pointer cannot be assigned to a non-const pointer" So in my compilers case (or the way that I am using it) the CONST keyword is no good, in this instance. Regards Marshall |
Topic | Author | Date |
Location of Pointers in XDATA | 01/01/70 00:00 | |
What does datasheet says? | 01/01/70 00:00 | |
RC-51 ref manual, pg 51 | 01/01/70 00:00 | |
ahh so easy when you read the instructions | 01/01/70 00:00 | |
xdata? | 01/01/70 00:00 | |
too? | 01/01/70 00:00 | |
Well yes actually - now that you mention it | 01/01/70 00:00 | |
what do you really want? | 01/01/70 00:00 | |
You are correct you supplied the answer as asked | 01/01/70 00:00 | |
wronk 'keyword' | 01/01/70 00:00 | |
const + code | 01/01/70 00:00 | |
the compiler is smart enough to ... | 01/01/70 00:00 | |
Compiler-specific? | 01/01/70 00:00 | |
It didn't actually compile with CONST | 01/01/70 00:00 | |
const is expected to catch non-const assigns![]() | 01/01/70 00:00 |