wouter van ooijen wrote:

>> So unless throw is specifically thread safe in a compiler I don't think
>> that it can be used in an interruptible environment.
> 
> Of course, anything that is not 'reentrant'-safe can not be used in both
> main and interrupts. But throw/catch can and should be fully reentrant.

I think Peter's point is that if you use a compiler in such an environment,
you better make sure that what you need is explicitly specified as
reentrant. It's just too easy for an implementation to use some static or
global variable somewhere behind the scenes to manage something -- and not
have it properly secured. 

The exception mechanism is probably one of those possible problem spots,
because by definition it has one single (global) exit point -- it usually
ends up in main() if an exception doesn't get caught. So where does that
leave the not caught interrupt exception? 

Gerhard

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist