----- Original Message ---- > From: David E. Wheeler <da...@kineticode.com> > > > And Test::Exception and many, many other Test:: modules. It's a very > > common > pattern and getting all authors to agree to fix those modules is a dubious > strategy, I think. > > /me shrug. If their modules fail with a new version of T::B, they have to fix > it, no? > > I'm inclined to think that this is not our problem.
None of them will fail with the new version of T::B (that I'm aware of). However, they'll fail with 'subtest', which means that for many serious test system (such as ours at the BBC which is where I found this error), subtests are needed, but useless. What if the T::B singleton held a weak reference to the child and if it's present, automatically calls the child's $Test->ok and $Test->diag? That will catch all of the cases I've seen. It might be a useful stop-gap measure, but it also seems dodgy as hell :( Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://use.perl.org/~Ovid/journal/ Twitter - http://twitter.com/OvidPerl Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
