| ??? 06/23/09 21:04 Read: times |
#166402 - Prototyping ISRs Responding to: ???'s previous message |
Mahesh Joshi said:
2. only prototype ISR in any of .h file which is #included in the file containing main() Andy Peters said:
Option 2 is the standard way of allowing functions in one file to call functions in another. True - but the 'C' source code never calls an ISR, does it? Therefore a prototype for an ISR seems somewhat meaningless I don't see this as a limitation of SDCC -- it's just how C works. I think the requirement for the ISR to be "visible" in the fille containing main() is purely an SDCC requirement? It certainly has nothing to do with 'C' in general. ('C' in general knows nothing about ISRs). |
| Topic | Author | Date |
| Pseudo timers make programming delays easy. | 01/01/70 00:00 | |
| volatile + racing condition | 01/01/70 00:00 | |
| slow processors | 01/01/70 00:00 | |
| You beat me to it... | 01/01/70 00:00 | |
| Timers_0.1 available. | 01/01/70 00:00 | |
| SDCC | 01/01/70 00:00 | |
| ISR defining with SDCC | 01/01/70 00:00 | |
| oh, I just read it in the manual | 01/01/70 00:00 | |
| only conditionally, as #ifdef SDCC | 01/01/70 00:00 | |
| SDCC and ISRs | 01/01/70 00:00 | |
| Prototyping ISRs | 01/01/70 00:00 | |
| you can see it as if.... | 01/01/70 00:00 | |
| SDCC Quirk? | 01/01/70 00:00 | |
internals of SDCC | 01/01/70 00:00 | |
| duh | 01/01/70 00:00 | |
| Too quick | 01/01/70 00:00 | |
| I see something else... | 01/01/70 00:00 | |
| That helped. | 01/01/70 00:00 | |
| Oops! Timers_0.2 available. | 01/01/70 00:00 | |
| you persist | 01/01/70 00:00 | |
| Good idea! | 01/01/70 00:00 | |
| atomicity | 01/01/70 00:00 | |
| No | 01/01/70 00:00 | |
| I gladly, click on a link .... | 01/01/70 00:00 | |
| Direct link | 01/01/70 00:00 | |
| that was clearly possible, I wonder why ... | 01/01/70 00:00 | |
| one more thing, now we are digging deep | 01/01/70 00:00 |