On Mon, Nov 10, 2014 at 6:00 AM, Dominik Vogt <[email protected]> wrote:
>> 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?
That test is run (all tests are run or explicitly skipped or marked
unsupported). In go-test.exp look for
$test_line == "// run cmplxdivide1.go"
Ian
