That's why I said you prefix with a ".". This has the effect of making it not a number as far as TAP is concernted, instead it becomes part of the name.
Of course it would be better to allow "."s in the number, that way you can check that they are increasing properly and allows you to have sub-plans (so each fork/thread/block can have it's own plan) rather than just having 1 single overall plan for the whole thing. Having 1 overall plan means that if one fork skips a test and the other does an extra test you won't notice. Given that x.x.x.x currently causes an error for TAP, changing the protocol to allow it would not break anything. But as I said, I wasn't proposing that - although I would be happy to see it, F On 3/28/06, Adam Kennedy <[EMAIL PROTECTED]> wrote: > > > What's changing the protocol? > > As I understand it from > http://search.cpan.org/~petdance/Test-Harness-2.56/lib/Test/Harness/TAP.pod > the test number must be a number. > > It does refer specifically to it having to start with a digit, but I'm > assuming that by number it means [1-9]\d* > > .1.2 would on the face of it seem to not match this pattern. > > Adam K >
