Dimitrie O. Paun [EMAIL PROTECTED] writes:
Now, on a different note, you pointed out an interesting thing: we need to
test mixed A/W cases. We thus have four possible cases:
(A,A), (A,W), (W,A), (W,W)
Should we test all of them?
We must test everything that is part of the expected
--- Dmitry Timoshkov [EMAIL PROTECTED] wrote:
Andriy Palamarchuk [EMAIL PROTECTED] wrote:
Attached version of the C testing framework, which
is
implemented with using TCHAR.H macros, so it is
portable between ASCII and Unicode platforms. Also
implemented test which can be used to
--- Dimitrie O. Paun [EMAIL PROTECTED] wrote:
I have a number of observations:
-- we should rename wt_helper.h to something like
wine/tests.h
I'm open for suggestions. I used this name to avoid
name clashes with Perl winetest framework. BTW, wt =
Wine Test.
I'd prefer more
Just commenting from the side-lines :-)
On Tue, 22 Jan 2002, Andriy Palamarchuk wrote:
[...]
Using function instead of macro won't work in all the
cases, e.g. in this one:
_TCHAR buf[100] = _T(foo)
I would rather avoid such constructs precisely because of the
compiler support
Andriy Palamarchuk [EMAIL PROTECTED] writes:
In the worst case people, who do not have such
compiler will be able to run tests in ANSII mode only.
That's clearly not an option.
Here I don't agree with you. Programming with TCHAR is
*exactly* the same as programming with WCHAR, but with
On Tue, 22 Jan 2002, Andriy Palamarchuk wrote:
--- Dimitrie O. Paun [EMAIL PROTECTED] wrote:
I have a number of observations:
-- we should rename wt_helper.h to something like
wine/tests.h
I'm open for suggestions. I used this name to avoid
name clashes with Perl winetest
On Tue, 22 Jan 2002, Alexandre Julliard wrote:
But we want people to think twice, and write a test adapted to the
function they are testing; you don't test ASCII and Unicode the same
way, except superficially.
With all due respect Alexandre, I can't understand your point. When does
the
Dimitrie O. Paun [EMAIL PROTECTED] writes:
With all due respect Alexandre, I can't understand your point. When does
the _semantics_ of the function differ based on the string
encoding???
Functions that take strings usually do something with them, so this is
part of the function semantics,
Attached version of the C testing framework, which is
implemented with using TCHAR.H macros, so it is
portable between ASCII and Unicode platforms. Also
implemented test which can be used to test ASCII and
Unicode API.
As I found out creating ASCII/Unicode portable code
requires much more