| ??? 09/27/07 06:41 Read: times |
#145018 - Rule breaking Responding to: ???'s previous message |
One rule that's easily misunderstood is keeping ISRs "short".
This means that the maximum execution path (and, thus, time) should be kept short - it doesn't necessarily mean that the total, overall code size of the entire routine needs to be "small". eg, an ISR might be a switch statement with a lot of cases, each of which is only "short" - so the overall routine could look quite "long", while any single path through it will only ever be "short". It can be argued whether this still breaks the "simple" rule, of course... |
| Topic | Author | Date |
| New FAQ III. | 01/01/70 00:00 | |
| Similarly for 'C' | 01/01/70 00:00 | |
| floating point | 01/01/70 00:00 | |
| "fixed point" FAQ by Erik Malund | 01/01/70 00:00 | |
| corrected FAQ | 01/01/70 00:00 | |
| on 3V3 and 5V | 01/01/70 00:00 | |
| when a RC "debouncing" circuit goes wrong | 01/01/70 00:00 | |
| basic interrupt hints | 01/01/70 00:00 | |
| the C hater | 01/01/70 00:00 | |
| better? | 01/01/70 00:00 | |
| very condensed but clear | 01/01/70 00:00 | |
| it's good sometimes to violate the rules | 01/01/70 00:00 | |
| Rule breaking | 01/01/70 00:00 | |
| The idea of keeping the ISR routine short... | 01/01/70 00:00 | |
| epanded | 01/01/70 00:00 | |
Exactly | 01/01/70 00:00 | |
| flags | 01/01/70 00:00 |