On 12 Mar 2007, at 12:27, Andy Armstrong wrote:
I don't want every producer written from here forward to have to be able to negotiate its way through a minefield of supported versions. From the producer's point of view the logic should be as simple as checking that the harness supports our version. If it doesn't emit a diagnostic and skip.
Actually I'm not even sure if I like the idea of the harness telling the producer what it can support. I'd say that if you want to produce TAP version 53 you have to have a harness that supports it. If the harness sees a version later than those it knows about it should display a warning and skip those tests completely.
Anything else takes us down the road of having a load of hard-to- maintain logic floating around in both producers and harnesses to find the highest common version and then attempt to work with it. Tests that can't reliably do what they want to do should fail - not mess about trying to work in a crippled mode.
-- Andy Armstrong, hexten.net
