Andrii, >> The main reason that all exceptions are caught there is because we do >> not want that an uncaught exception from one session terminates the >> entire application (and therefore all sessions), but I understand that >> you sometimes want that behaviour during development. >> > > In case if this behavior (whole application core dump with aborting all > the sessions) is unwanted - wt user could launch each session in new > process. > AFAIK, wt supports this.
Correct, but this is of course expensive (memory-wise). > Or, application developer could catch all exceptions in code my himself. > Anyway, either this or that leaves some options for developer. But right > now there are no options:) > The catch-all clause is there as a safety measure because there really shouldn't pass any exceptions past that point. But you have a point, and it would be nice to provide a means to override this, which is currently impossible. In the meantime, did you consider set_new_handler()? And just out of curiosity, the man page of malloc() states that _malloc_options = "X" should call abort() rather than throw an exception. Does it behave different than specified? Best regards, Wim. ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
