> 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.

That is essentially a strawman argument: bad implementations exist (or
could exist), so the language feature is bad. 

> 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? 

I am not familiar with the semantics of propagating an exception out of
the exception handler, but if from your interrupt hndler you will use
anything that can throw an exception you'd better include an appropriate
handler - and at least for debugging one at the top that flashes some
aleam if and exception propagates up to there!

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
 
 

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