??? 06/17/05 18:01 Read: times |
#95204 - const Responding to: ???'s previous message |
In other compilers const can refer to the memory space as well (code in Keil), so you can have a const pointer (a pointer that cannot point to any other address) pointing to const data (can't modify the data). Some compilers use the latter to indicate ROM space.
Dan Saks has a ton of fun stuff like that at ESP mag: http://embedded.com/showArtic...ID=9900041 (Caveat: That particular article is more about C++ and references than C pointers, but it's a "fun" read). Google Saks, const, ROM and the like for more interesting reads... GB |
Topic | Author | Date |
Const Array Store at a Specific Address | 01/01/70 00:00 | |
Initializing constant location. | 01/01/70 00:00 | |
KEIL uVision 2 C51 6.10 | 01/01/70 00:00 | |
No Linker? | 01/01/70 00:00 | |
Linking Mike | 01/01/70 00:00 | |
Linker's Job | 01/01/70 00:00 | |
Cannot you use something like.... | 01/01/70 00:00 | |
in fact | 01/01/70 00:00 | |
Keil | 01/01/70 00:00 | |
seems it cannot be done in C with Keil | 01/01/70 00:00 | |
Done in 'C' with Keil | 01/01/70 00:00 | |
Linker job | 01/01/70 00:00 | |
Linker's Job | 01/01/70 00:00 | |
Intel Hex | 01/01/70 00:00 | |
Accessing Code Arrarys | 01/01/70 00:00 | |
Why so complicated? | 01/01/70 00:00 | |
Memory space | 01/01/70 00:00 | |
Oops! | 01/01/70 00:00 | |
No can do | 01/01/70 00:00 | |
To Steve/Craig | 01/01/70 00:00 | |
Punisment? | 01/01/70 00:00 | |
I'll just nip nack to last week and... | 01/01/70 00:00 | |
Some would | 01/01/70 00:00 | |
I have the impression that | 01/01/70 00:00 | |
a small problem with this that many have | 01/01/70 00:00 | |
using constant | 01/01/70 00:00 | |
const![]() | 01/01/70 00:00 |