Vincent Povirk wrote: > Ok, but my point is (and I'm not saying we should necessarily do > this), according to the Wine Developer's Guide an err is something > that we should be concerned about, by definition. If we buy this, and > some current err messages are often harmless, implying no loss of > important functionality, they should be changed to some other channel.
For a normal App I'd almost agree with that (unless of course App does some invalid stuff which some do). For the test - no. Lots of tests probe border cases as well as invalid conditions. Wine is 100% correct to complain about such situations. However that's precisely what's being tested. All tests should be written to examine one thing at a time. And most are. If test doesn't fail, everything else is irrelevant. Vitaliy
