> But it seems to me that exceptions are more like "come-from" 
> than "go-to".  That is, you see clearly where the exception 
> is handled, but you don't know where it is thrown.

In an abstract but important way you do know: within the scope of the
catch block. (Or by a fucntion called from within, but that is
essentially the same.) A lot of things (unwidning, freeing up
recsources) can be done between the throw and the catch. If you feel
like you need to know exactly where the exception was thrown then the
construct was used badly.

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