Stuart Henderson wrote:
> On 2009/08/16 06:33, James Wright wrote:
>
>> Luckily there is a solution that seems to work around this problem
>> without requiring Test::More in base to be updated.
>>
>
> Wouldn't it be easier and more useful to just update Test::More in base?
>
>
>
Yes it would, I just figured this would be a good stop-gap for those
people faced with this issue until that happens (especially those with
their own private ports tree). Also I guess I am not a big fan of
dual-use module updates being relied upon by downstream CPAN modules
without those updates being in a perl release, especially a change like
this which is essentially just existing functionality re-implemented in
a different way.
