On 5/13/05, Paul Koning <pkoning at equallogic.com> wrote:
it
twice. Embedded systems programmers are painfully
familiar with this.
Well I don't know how painful I've found it (as an embedded systems
programmer). An interrupt is just another event source, albeit one
that must be handled with kid gloves. Your program will follow
different paths depending on the events inputs to it. Just because you
don't understand what has happened if you do a poor job on your
interrupt handler doesn't mean that the outcome isn't completely
predictable based on analysis of the code and understanding how the
machine works.
I have heard of systems where a randomness is allowed in: for example,
cases where FPGAs + genetic programming are used to evolve an
algorithm. It turns out that this can work, but unless you take
special measures you will end up with strange dependencies on noise
from the power source, etc.
-- John.