| ??? 06/16/06 11:10 Read: times |
#118401 - Yes,very atomic Responding to: ???'s previous message |
The link that Charles references conveniently ignores atomicity issues. It can probably get away with this as it uses byte variables but that doesn't always mean you're home free! What happens if you want to read the whole time for processing or whatever and you read the hours then in the meantime the interrupt has just clocked over your minutes from 59 to 0 then you read the minutes - if its just for display, then for one display cycle the display will be wrong! But the average human will not pick that. It seems a lot of the published code I see seems to ignore atomicity issues - obviously it isn't well known but the effects can be random and hard to track down. Thanks Andy for the correction, do I get an elephant stamp anyway? |
| Topic | Author | Date |
| Timer0_ISR delay troubles | 01/01/70 00:00 | |
| Why it doesn't work | 01/01/70 00:00 | |
| Extra Atomic | 01/01/70 00:00 | |
| Been there Done That | 01/01/70 00:00 | |
| Yes,very atomic | 01/01/70 00:00 | |
| nuclear explosions | 01/01/70 00:00 | |
| Also | 01/01/70 00:00 | |
| Thanks everyone | 01/01/70 00:00 | |
| learn to swim before diving in | 01/01/70 00:00 | |
| using 1 | 01/01/70 00:00 | |
| Some code from the prof broke interrupt | 01/01/70 00:00 | |
| Nevermind | 01/01/70 00:00 | |
| which it is not | 01/01/70 00:00 | |
Explain? | 01/01/70 00:00 | |
| What happend to common sense? | 01/01/70 00:00 | |
| specific examples are dangerous | 01/01/70 00:00 | |
| Uncommon Sense | 01/01/70 00:00 | |
| Practical programming | 01/01/70 00:00 | |
| Charles | 01/01/70 00:00 |