Improved interrupt handling

[Desterline]

Seems they culd improve the way interrupts are handled.

The latency of the ON INTERRUPT methodology is undesirable. The excelent code from Tim Box that stores all the complier internal variables, allowing for picBasic instructions in an assembler interrupt, improves this. However, a simple interrupt may not use all of those variables, so saving and restoring all of them is excessive. It seems the compiler could make an inteligent decision on which ones need saved and create the neccesary code.

Or, the compiler could use duplicate macros when a function is called in an interrupt routine.

Perhaps the best solution would be a configurable combination of these options. The reletive speeds and resource utilization of the potential solutions could be presented to the user, then the user could decide which one to go with.

Anybody have any thoughs on that?
-Denny