| ??? 05/13/08 16:14 Read: times |
#154734 - Sorry but.. Responding to: ???'s previous message |
an ISR should "almost always" do NOTHING except tell main() what to do.
Yes it is not common, but when an an interrupt requires a response with tight timing, and main does not have such constraints it may be better. And yes this is the very rare exception. Sometime you can not blindly follow the guild lines. But understand why they are there. |
| Topic | Author | Date |
| Struct member losing value | 01/01/70 00:00 | |
| Please post your code | 01/01/70 00:00 | |
| Posted here (along with file descriptions): | 01/01/70 00:00 | |
| the can of worms | 01/01/70 00:00 | |
| Your program needs to be restructured | 01/01/70 00:00 | |
| Can't mod this one up enough. | 01/01/70 00:00 | |
| Thanks for the tips | 01/01/70 00:00 | |
| You're doing pretty good then. | 01/01/70 00:00 | |
| I think that it can be said in a simple way | 01/01/70 00:00 | |
| Sorry but.. | 01/01/70 00:00 | |
| Agreed | 01/01/70 00:00 | |
| the phrase was | 01/01/70 00:00 | |
| I agree | 01/01/70 00:00 | |
| Don't ignore rules | 01/01/70 00:00 | |
| What is "short" in an ISR...? | 01/01/70 00:00 | |
| Two Program | 01/01/70 00:00 | |
breaking switch/case | 01/01/70 00:00 | |
| Do you understand why? | 01/01/70 00:00 | |
| make it a FAQ, please... | 01/01/70 00:00 |