> I'd still like to avoid the rampant duplication if possible. One > approach would be to put most of the test in something like > nilptr_tests.go marked with "// skip". Then we can have top-level > nilptrXX.go tests with +build lines that use "// run nilptr_tests.go".
I fail to see how that could be done with "// run". There is one example use, namely cmplxdivide.go". That is not run in gcc because the "run" line does not match anything in go-test.exp. If I add a rule for that, how does that help me to compile a test that consists of multiple files? At the moment, I've no idea how to tackle the multi file problem with the existing go-test.exp. Ciao Dominik ^_^ ^_^ -- Dominik Vogt IBM Germany
