Re: Does signal trap of CTRL-CLOSE event allowable to be used on windows?

[Tatsuro MATSUOKA]

Hello

--- On Thu, 2011/7/14, Michael Goffioul  wrote:

> The main problem with these signals in Win32 is that they
> are not executed in octave main thread, but in a separate
> thread. The pain is then to make the main octave thread to
> jump at a specific code to execute from the thread handling
> the signal. This is what the CTRL-C handler is trying to do,
> but fails 50% of the time.
> 
> Although in the case of CTRL_CLOSE_EVENT, we might
> tolerate to exit octave from the signal thread instead of the
> main thread, but I wouldn't bet on a safe exit, especially if
> some exit handlers have been installed.

Safe exit perhaps cannot be implemented to CTRL_CLOSE_EVENT.
Which do you think better pressing  [x] button causes error message outside of 
octave or pressing  [x] button causes causes internal octave but not cause 
external error message?

Regards

Tatsuro