| ??? 12/06/04 08:58 Read: times |
#82585 - reentrant Responding to: ???'s previous message |
Use keyword reentrant next to function prototype and definition. Be sure to read-up about how reentrant functions are implemented - this will incur a significant overhead that may well be inappropriate in an ISR... It may well be more appropriate to re-think the code so that you are not calling functions from both interrupt & "main" code... |
| Topic | Author | Date |
| 89s52 function sharing. | 01/01/70 00:00 | |
| Try This | 01/01/70 00:00 | |
| emphasis | 01/01/70 00:00 | |
| an idea... | 01/01/70 00:00 | |
| Andy, I tried it | 01/01/70 00:00 | |
| Jolly good! | 01/01/70 00:00 | |
| Error | 01/01/70 00:00 | |
| You need to work on it | 01/01/70 00:00 | |
| reentrant ? | 01/01/70 00:00 | |
| reentrant | 01/01/70 00:00 | |
| non-reentrant | 01/01/70 00:00 | |
| Wow | 01/01/70 00:00 | |
| varaible sharing? | 01/01/70 00:00 | |
| Variable sharing | 01/01/70 00:00 | |
| Overflow | 01/01/70 00:00 | |
| variables, main and ISR | 01/01/70 00:00 | |
| Globals use more memory | 01/01/70 00:00 | |
| Isn't that a global? | 01/01/70 00:00 | |
Globals, ISRs, main, & static | 01/01/70 00:00 |