??? 05/19/08 13:24 Read: times Msg Score: +1 +1 Informative |
#154902 - gobbelygook Responding to: ???'s previous message |
When we use the word Optimise, we mean that the variable in the memory can be changed only by the compiler whenever the code is executed
the compiler can change NOTHING "when the code is executed" once the code is linked, the tools have nothing to do with what happens During linking process the code is allocated physical memory in the internal memory. so during the link process( generation of .lnk file during compilation) these variables are placed in the heap instead of main memory 1) what '51 compiler produces .lnk 2) WHAT 'heap' 3) NOTHING is placed in "main memory" (whatever that is) during linking, no memory is loaded till you download. Compiler cannot modify the variable until unless a copy is copied to RAM for execution. the compiler can NEVER "modify the variable" When a memory is optimised, then the life of that variable is limited only till the function executes then it is destroyed that is the case whether "memory is optimised" or not. if not then i can still continue my explaination in my next post Please don't Erik |
Topic | Author | Date |
keyword volatile | 01/01/70 00:00 | |
Opposite! | 01/01/70 00:00 | |
volatile modifier | 01/01/70 00:00 | |
Incorrect | 01/01/70 00:00 | |
incorrect! | 01/01/70 00:00 | |
even more | 01/01/70 00:00 | |
A heap o' trouble | 01/01/70 00:00 | |
the curse of the PC programmers | 01/01/70 00:00 | |
meaning of "volatile" with example | 01/01/70 00:00 | |
example | 01/01/70 00:00 | |
gobbelygook | 01/01/70 00:00 | |
heap? | 01/01/70 00:00 | |
Confused? | 01/01/70 00:00 | |
Google told me... | 01/01/70 00:00 | |
link | 01/01/70 00:00 | |
go through my explanation | 01/01/70 00:00 | |
put simply... | 01/01/70 00:00 | |
thanks | 01/01/70 00:00 | |
answer accepted by interviewer | 01/01/70 00:00 | |
Not entirely | 01/01/70 00:00 | |
not input only | 01/01/70 00:00 | |
That's the kind of thing I'd be looking for...![]() | 01/01/70 00:00 |