| ??? 05/17/08 20:01 Read: times |
#154852 - which, even when possible, often is ill advised Responding to: ???'s previous message |
Probably the biggest effects of this are on calling functions from main & interrupt code
I remember an intermittent problem in a PC program that I traced to the above. A 'shared' variable got screwed up. Yes, before Windows, I did dabble with the PC, probably 10000+ lines of it. The, horray, I got enough '51 work to forget all about the PC. Erik |
| Topic | Author | Date |
| "Real C" vs '51 C | 01/01/70 00:00 | |
| there is nothing wrong except... | 01/01/70 00:00 | |
| if you are not , why are you even here | 01/01/70 00:00 | |
| *(buffer+8+index)? | 01/01/70 00:00 | |
| none of the above | 01/01/70 00:00 | |
| OK then how? | 01/01/70 00:00 | |
| like this | 01/01/70 00:00 | |
| but it's basically the same... | 01/01/70 00:00 | |
| YCMV | 01/01/70 00:00 | |
| No | 01/01/70 00:00 | |
| assumptions | 01/01/70 00:00 | |
| Re: assumptions | 01/01/70 00:00 | |
| I took a \'known\' example | 01/01/70 00:00 | |
| Compiler-independent efficient C | 01/01/70 00:00 | |
| a clarification and an example | 01/01/70 00:00 | |
| Two kinds of "efficiency" | 01/01/70 00:00 | |
| Compiler smarter than coder | 01/01/70 00:00 | |
| Getting the least out of your compiler | 01/01/70 00:00 | |
| Real C is inherently reentrant | 01/01/70 00:00 | |
which, even when possible, often is ill advised | 01/01/70 00:00 |