C++ tests (1/2)
ps at leissner.se
Fri Nov 15 11:40:30 CST 2002
> Patrik Stridvall <ps at leissner.se> writes:
> > So my questions to you:
> > 1. Should we support the C++ only features meantion above?
> > 2. If yes, should we just include it in the tree without tests
> > and just hope it works or should we have C++ tests for them?
> When someone has an app that requires these features they can
> implement them, and test them by building their app. Or we can
> implement them and write a small test program to test them once.
The same can be said about every "C" feature as well.
> need to build a new test environment for such uncommon features.
Many normal "C" features are not commonly used either, shouldn't we
have tests for them?
Look, the point of tests is not testing once. It is testing for
regressions when the code changes.
> > I see no relevent comparsion between them:
> > 1. C++ is actually used by the Microsoft SDK. Perl is not.
> > 2. The Perl framework was big and required generated modules.
> > The C++ framework is very small and uses the Wine header files
> > as they are (or should be in order to be Microsoft compatiable)
> The issue is not really the size of the framework, it's the extra
> dependencies. It would require everybody who wants to run tests to
> have a working, compatible C++ installation; given the various levels
> of brokenness of existing g++ versions that's far from trivial.
Very true. Thanks for reminding me that it should be an optional feature.
It you want to use it:
More information about the wine-devel