On Jul 9, 2008, at 01:13, Eric Wilhelm wrote:
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?
Yes, good catch. Pasto.
(For some value of 'work' --
# 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, t
On Jun 18, 2008, at 11:07, Eric Wilhelm wrote:
Link?
http://www.nntp.perl.org/group/perl.module.build/2008/03/msg1298.html
Wow, that's pretty comprehensive. I'm afraid that I'm much too lazy to
implement plugins as described there. Besides, to get Module::Build to
do what I want, I'd st
On Jun 18, 2008, at 11:07, Eric Wilhelm wrote:
http://www.nntp.perl.org/group/perl.module.build/2008/03/msg1298.html
There are more if you point your favorite search engine at
nntp.perl.org/group/perl.module.build and ask about plugins.
Thanks, I'll take a look.
How hard can it be? (He ask
# from David E. Wheeler
# on Wednesday 18 June 2008 07:54:
>On Jun 18, 2008, at 01:57, Eric Wilhelm wrote:
>>> so I guess that subclassing isn't
>>> necessarily the best way to go.
>>
>> Do you have enough tuits to dust-off the "plugin architecture"
>> thread?
>
>Link?
http://www.nntp.perl.org/
On Jun 18, 2008, at 01:57, Eric Wilhelm wrote:
so I guess that subclassing isn't
necessarily the best way to go.
Do you have enough tuits to dust-off the "plugin architecture" thread?
Link?
How hard can it be? (He asks, ignoring the dragons.)
Subclassing is not a great way to do mixins by
# from David E. Wheeler
# on Tuesday 17 June 2008 15:24:
>so I guess that subclassing isn't
>necessarily the best way to go.
Do you have enough tuits to dust-off the "plugin architecture" thread?
Subclassing is not a great way to do mixins by multiple authors,
especially if the interface is l
Howdy,
I've just sent a patch to Andy Armstrong for TAP::Harness that will
allow me to mix different kinds of tests in a single harness (Perl,
Ruby, SQL, whatever), just as long as they all emit TAP, of course.
I'd like to take advantage of this in my Build scripts. It looks like
the simp
