in reply to Re: Re: Re: Re: Closures, object destruction and memory leaks
in thread Closures, object destruction and memory leaks

If your signal handler doesn't do much, then that is probably the right way to do things. And on reflection, having signal handlers not do much is generally the right way to do things.

My thinking was in case your signal handler did something irrevokable like try to exit, in which case you should allow people to catch it. But if you don't, then don't worry about it. :-)

  • Comment on Re: Re: Re: Re: Re: Closures, object destruction and memory leaks

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Re: Closures, object destruction and memory leaks
by mpeppler (Vicar) on Nov 11, 2003 at 16:18 UTC
    Ah - I see your logic. No, in a library module I always want to leave as many options as possible to the caller, so calling exit() from the handler isn't something that I'd consider a good idea :-)

    Michael