Sean Kelly wrote:
I don't know if this is how you did it, but one option would be to have the unittest code set a custom assert handler, then reset it when done. The problem with this has historically been that DMD didn't generate a valid callstack for returning normally from an assert failure (for runtime code efficiency, I believe).
The call stack is valid for the unittest calls. You're right that it is not for asserts.
_______________________________________________ dmd-internals mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/dmd-internals
