PureUnit should run only one combine too
Posted: Wed Nov 26, 2008 7:35 pm
Now PureUnit is in the official package so i think we can make feature-requests for this 
I'm kidding ... the request i would have also if it wouldn't be
The current version is still "PureUnit03"?
PureUnit wants to compile the code always in every combination of the
possible options. This is good for you, but not for us. If we create a
program with threads, we doesn't need to test it without threadsafe. Or i
use only unicode and something don't run in ascii, so PureUnit will
always fail.
... there should be a way to say which combinations i want
to run.
The second, but more a "nice to have" as a "must have" for me is the
behaviour of the PureUnit-Macros in IDE. It works well if i compile it without
debugger. As expected the message shows all you need but if i try
it with debugger the message shows only "failed" and not the
message i want for it. Could you change this too?
Please submit the changelog like normal pb-freatures in the helpfile, so i
doesn't miss it.
MFG PMV
I'm kidding ... the request i would have also if it wouldn't be
The current version is still "PureUnit03"?
PureUnit wants to compile the code always in every combination of the
possible options. This is good for you, but not for us. If we create a
program with threads, we doesn't need to test it without threadsafe. Or i
use only unicode and something don't run in ascii, so PureUnit will
always fail.
... there should be a way to say which combinations i wantto run.
The second, but more a "nice to have" as a "must have" for me is the
behaviour of the PureUnit-Macros in IDE. It works well if i compile it without
debugger. As expected the message shows all you need but if i try
it with debugger the message shows only "failed" and not the
message i want for it. Could you change this too?
Please submit the changelog like normal pb-freatures in the helpfile, so i
doesn't miss it.
MFG PMV