We've been down this road before, haven't we, Jim? That never stopped me, though. :)

>Everyone is right here. Anything that ASSERT is cofirming should be handled also by an error handler

OK, I just think that the common practice is not to do this. For example, an ASSERT that traps a logical condition that will not cause the program to crash. Programmers add these and think they're being safe, but that safety is removed on release unless the test is duplicated.

>It may seem like double work, but for frameworks (for one example) it is very nice to give the developer a message saying a certain parameter should be character. The developer can then go to the debugger and change the parm's value and finish the testing run without exiting and recoding and rerunning the app.

That makes good sense. Could the same error handler that the user sees do this as well, in development mode?