Test::Harness features

[Eric Wilhelm]

# from David Golden
# on Tuesday 09 June 2009 10:50:

>On Tue, Jun 9, 2009 at 12:52 PM, Eric Wilhelm wrote:
>>I considered Test::Harness deprecated and TAP::Harness
>> to be the new entry-point for adding features.
>
>That's not what I'm talking about.

Maybe I missed something?  Please explain your use-case.

>It's 'deprecated' for new development, but it's not deprecated in
>general usage due to the same back-compatibility problems that plague
>the rest of the toolchain.  (Hurrah for configure_requires, but we'll
>be 10 years before we can assume it as standard.)

It sounds like you're wanting to plugin to TAP::Harness via 
Test::Harness using environment variables while running an arbitrary 
(generated Makefile) `make test` with EU::MM and/or the Makefile.PL 
being none the wiser.  I'm thinking "Dragons! Run away!!!"

>So my suggestion is to fix the back-compatibility so that it's easy to
>(a) use features already in TAP::Harness and (b) use new features in
>TAP::Harness extensions or plugins.

If one wants TAP::Harness features, one must require TAP::Harness to 
make them work, at which point I fail to see why Test::Harness needs to 
be involved.  The Test::Harness layer is a bottleneck to whatever knobs 
you're needing, and throws in some dealbreaker assumptions as a bonus.

I thought build_requires and such would give plenty of room to assert 
and install a worldful of deps (thus allowing all of the shiny new 
knobs and levers to be manipulated directly), but maybe I'm missing 
what you're trying to accomplish.

--Eric
-- 
Anyone who has the power to make you believe absurdities has the power
to make you commit injustices.
--Voltaire
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------