Re: Subclass? Plugin? Mixin? Monkey Patch?

# from David E. Wheeler
# on Thursday 19 June 2008 12:25:

>* Adds the `use_tap_harness` property. This forces Module::Build to  
>use TAP::Harness to run tests instead of Test::Harness. This is  
>potentially very powerful, because it gives uses much more control  
>over their test environments, thanks to the other new property…

Shouldn't this be:

  __PACKAGE__->add_property(use_tap_harness => 0);

(instead of)
  __PACKAGE__->add_property(use_tap_harness => {});

So the --use_tap_harness=1 command-line option will work?

(For some value of 'work' -- that's a major wreck right now for 
Module::Build's tests -- some assumption about blib/lib is wrong?)

--Eric
-- 
"Left to themselves, things tend to go from bad to worse."
--Murphy's Corollary
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------