Graeme Geldenhuys schreef:
Oh, I forgot to mention. If the ObjectStates match, the test passes
fine, and doesn't give an access violation.
While creating the new AssertEquals method, I purposefully created a
failure with then gives the access violation, instead to the
comparison message I expected:
"Failing on 1: Expected <posClean> but got <posEmpty>"
Try creating a back trace, maybe that gives some insight.
Vincent
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
