--- Steffen Mueller <[EMAIL PROTECTED]> wrote: > Andy Lester schrieb:
> > That's why this is gonna be 3.0. Break the API all you want. > > Woah there! This is still going to be on CPAN and pushed to all > clients > semi-automatically. A year ago or so, a bug in a single Test:: module > cascaded through half of CPAN. That wasn't pretty at all. We can fix > most CPAN modules, of course, but what happens to "darkpan" is just > way beyond us. I suspect what Andy was meaning was that it's OK to break the underbelly of Straps, Point, etc., and not the actual Test::Harness API, since it's the former I was referring to. TAPx::Harness::Compatible is still intended to pass all of the Test::Harness tests. However, I'm not sure what to do about darkpan reliance on things they shouldn't be relying on. The current testing framework is simply too limited and most acknowledge that something new needs to come along. However, it's going to be awfully tough to come up with something new if we don't change *something*. I'm just worried about what it is we can safely change. Do Test::Smoke, CPAN, CPANPLUS or anything similar rely on the actual guts of Test::Harness? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
