How to handle assert() in Windows GUI apps?

Kagamin spam at here.lot
Fri Apr 8 04:29:37 PDT 2011


Jonathan M Davis Wrote:

> On 2011-04-07 14:19, Andrej Mitrovic wrote:
> > Everything works fine now, please disregard my silly thread. :)
>  
> Well, whatever you're doing, you almost certainly shouldn't be catching Errors 
> (AssertErrors or otherwise). That's generally a very bad idea. Very little 
> cleanup is done when Errors are thrown. finally blocks get skipped. scope 
> statements get skipped. Destructors get skipped. Etc. So, once an Error is 
> thrown, it takes very little for the program to be in an invalid state.

hmm, docs say different things:

> If code detects an error like "out of memory," then an Error is thrown with a message saying "Out of memory". The function call stack is unwound, looking for a handler for the Error. Finally blocks are executed as the stack is unwound. If an error handler is found, execution resumes there. If not, the default Error handler is run, which displays the message and terminates the program.


More information about the Digitalmars-d-learn mailing list