| ??? 07/08/08 21:29 Read: times |
#156544 - do NOT "put them" Responding to: ???'s previous message |
so my issue is what is the best way to write/tell/force C to put these arrays in spots that hopefully won't get corrupted.......or would it be a better idea just to have these arrays as global variables.
do NOT "put them", the compiler/linker does a far better job. As any C book will tell you the only variables that do not get willy-nilly overwritten are "global variables" and "static variables". A group of "Real C" phanatics will tell you not to use global variables and then they will have a major structure in main() the pointer to which is passed around to have global variables without calling them that. erik |
| Topic | Author | Date |
| Data Array getting corrupted after init | 01/01/70 00:00 | |
| OnePossibleIdea.... | 01/01/70 00:00 | |
| I did not do anything with the stack | 01/01/70 00:00 | |
| As Michael said.... | 01/01/70 00:00 | |
| How do you test and debug code? | 01/01/70 00:00 | |
| Keil is the only thing in place | 01/01/70 00:00 | |
| 'crap'?? | 01/01/70 00:00 | |
| Is this the book you refer? | 01/01/70 00:00 | |
| nope | 01/01/70 00:00 | |
| Erik | 01/01/70 00:00 | |
| So where is the code | 01/01/70 00:00 | |
| do NOT "put them" | 01/01/70 00:00 | |
| Focus | 01/01/70 00:00 | |
| Simulator | 01/01/70 00:00 | |
| So this is on a simulator? | 01/01/70 00:00 | |
| Post your duff code | 01/01/70 00:00 | |
| Finding Cause of Corruption | 01/01/70 00:00 | |
| Get the C right, then look at the target CPU | 01/01/70 00:00 | |
| Optimizing Compilers | 01/01/70 00:00 | |
| In my experience..... | 01/01/70 00:00 | |
| Keil C 51 Optimizations | 01/01/70 00:00 | |
| Use IAR then | 01/01/70 00:00 | |
| different approaches | 01/01/70 00:00 | |
| sometimes, depends | 01/01/70 00:00 | |
Thanks | 01/01/70 00:00 |