Acces Violation: assert with null instance
Frank Benoit (keinfarbton)
benoit at tionex.removethispart.de
Fri Jan 26 02:34:46 PST 2007
> Conceptually, assert (expression) is nothing more that "if (!expression)
> throw new AssertError;". However, it doesn't act that way.
I think it is more like
if ( expression != 0 )
throw new AssertError;
that means .opEquals is called probably on a null reference, and so the
segfault is caused.
Hm...
Or is that what '!' does?
More information about the Digitalmars-d-bugs
mailing list