[DGD] Catching error on its own

Felix A. Croes felix at dworkin.nl
Wed May 25 13:13:01 CEST 2005


=?ISO-8859-1?Q?Petter_Nystr=F6m?= <md1pette at mdstud.chalmers.se> wrote:

> I have a situation where I get an error caught without there being any 
> catch statements. (That I have found atleast.) Just had a creeping 
> suspicion that I thought I could try to get verified here before doing a 
> closer inspection with debugs everywhere. The suspicion being that errors 
> that propagate to code in the driver object is always catched there? Catch 
> statement or not. (Because I have none.)
>
> Any other ideas? The code where the error occurrs is in my object daemon, 
> when I am about to unregister a program. The trace starts in 
> destruct_object(), but is invoked indirectly by DGD through the 
> remove_proram() function in the driver object.

This behaviour is documented in dgd/doc/Introduction.  remove_program()
is called by DGD in situations where errors are simply not allowed.

Regards,
Dworkin



More information about the DGD mailing list