| ??? 06/23/09 21:56 Read: times |
#166405 - SDCC Quirk? Responding to: ???'s previous message |
Jan Waclawek said:
.... the main() function would be the "bearer" of the interrupt vector, which in turn does *call* the ISRs. Yes, I dare say it's something like that. Maybe someone who knows the internals of SDCC will be along soon to explain it to us... Although this is a quirk of SDCC, I don't think it's a completely unreasonable one. Certainly including *prototypes* of ISRs shouldn't hurt in other dialects of C, either. I'd have thought not, but... However, the general principle of modular programming is to avoid publishing anything more widely than necessary. Many Keil people make it their practice to declare ISRs as static - so that a prototype really is meaningless! |
| 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 |