I thought this was the way it worked! It needs to work this way, because often
times, further parts of the same unit test depend on the prior parts passing.
I assumed that assert was still throwing, and being caught outside the unit
test. Something like this would be fine:
unittest
{
x = new X;
assert(x);
x.foo();
}
translates to:
unittest
{
try
{
x = new X;
assert(x);
x.foo();
}
catch(AssertionError e)
{
printAssertion(e);
}
}
-Steve
----- Original Message ----
> From: Andrei Alexandrescu <[email protected]>
> If you do want to improve
> things, please have assert abort the current unittest and continue to the
> next
> one. The current semantics is
> unbearable.
_______________________________________________
dmd-internals mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/dmd-internals
