> though, if we're going to forbid its use, it should > be even more effective to check if it is set to anything other > than 0 somewhere in the testsuite common code, so that the person > writing the test gets a loud bark from the testsuite before even > posting the patch. :-) I thought about that, but most testcases set it to zero... -- Joel