We *really* need a development model change !

[Alexandre Julliard]

Andreas Mohr <andi at rhlx01.fht-esslingen.de> writes:

> Hmm, and different "winver" settings for testing of the behaviour of
> different Wine --winver settings and adapting to different Windows versions
> are possible with this framework, too ?

In its current state it uses the default Wine config from ~/.wine so
any config changes can be done this way (of course we will have to
support -winver in the config file, but we need that anyway). We could
provide a set of standardized configs to reduce variation, but it may
in fact be preferable to let people run with the config they normally
use, so that we have a wider coverage of the different options.

> Oh, and what about Win16 support of the test suite ?

Not supported yet, though this could be added. In fact since the Perl
layer already needs to convert the arguments, making it support 16-bit
should be relatively easy, and probably a lot more transparent than
doing it in C.

> Still, I think we should try to have a C "compatibility" layer, too, for
> two reasons:
> - people who aren't familiar with anything else
> - supporting diversity (what if someday we find out that perl "sucks" ? :-)

If it turns out Perl doesn't work, we can always convert the tests to
C, this should be relatively easy. Most of the tests will simply be a
bunch of function calls and result checks, which is simple to do in
any language. Besides, unless you want to do elaborate tests, you
really don't need to know much Perl to be able to write tests with
winetest.

-- 
Alexandre Julliard
julliard at winehq.com