Test::Harness features

[Andy Armstrong]

On 9 Jun 2009, at 22:40, David Golden wrote:
> On reflection, I have a couple proposals for what to do about
> Test::Harness.  Essentially, Test::Harness is just a wrapper around
> TAP::Harness. The "problem" is that there has been no easy way to use
> anything other than TAP::Harness and there's been no way to extensibly
> provide arguments to the TAP::Harness constructor.

[snip]

Am I right in thinking that you're only advocating exposing an  
interface through Test::Harness because of other, extant parts of the  
tool chain that don't know about TAP::Harness?

-- 
Andy Armstrong, Hexten