--- 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
Hello,
I found a very interesting article about WINE there:
http://www.desktoplinux.com/articles/AT5502857506.html
I have to fully agree with that author, I think he is a real genius! :)))
Roland
--- 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
On Mon, 21 Jan 2002 [EMAIL PROTECTED] wrote:
Sometimes, not often, these sessions can fail for no
good reason, or at least not one that has anything to do with program
code on this end. I thought maybe trace was changing the timing of
things, so I tried the app without a trace, but with
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,
