On Friday 16 September 2005 19:34, Mark Ethan Trostler wrote:
> Alls you need to do is call:
> ($tot, $failedtests) = Test::Harness::_run_all_tests(@tests);
> instead of 'run_tests' to get at the '$tot' & '$failedtest' hash refs
> (Data::Dumper it or look at the comments in Test::Harness) which has all
> the info you need to output whatever/however you want - I use it to
> XML-ize Test::Harness output instead of the standard format.
> This also avoids the call to '_show_results' (or you can call it
> yourself later) so you can output whatever/however you want.
Hmmm... I've inspected the Test::Harness source now. While one can indeed do
what you said, if I want to emulate the functionality of _show_results in its
entirety, except for a small difference, then I'll have to duplicate a lot of
code. That's Not Good<tm>.
So I think a spin-off of Test::Harness which will facilitate doing that is
still in order.
Regards,
Shlomi Fish
> Mark
>
> Andy Lester wrote:
> > On Fri, Sep 16, 2005 at 11:35:05AM -0400, David Golden
([EMAIL PROTECTED]) wrote:
> >>I think a polite question is wonderful (with potential answers ranging
> >> from "sure" to "hey, that's a cool idea, let's try a merge instead of a
> >> fork").
> >
> > Sure, it's a polite question, but an unnecessary one. He can do
> > whatever he likes with the source.
> >
> > Just color me skeptical. As soon as there's something tangible for me
> > to say "Hey, let's try a merge instead of a fork" about.
> >
> > Email lists make it easy for people to say "hey I've got this great
> > idea", and people to pile on and say "That's good, that's bad" and we're
> > left with a lot of hot air and precious little code.
> >
> > So, Shlomi: Show me the code.
--
---------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Homepage: http://www.shlomifish.org/
95% of the programmers consider 95% of the code they did not write, in the
bottom 5%.
