chromatic wrote:
On Monday 26 February 2007 06:35, Christopher H. Laco wrote:
Or me. I have a personal hate relationship with MockObject in this way.
I love MockObject. I hate getting warnings about 3 party modules use of
can in my test suite.
Ideally those third parties would fix their buggy code, but after countless
messages, a couple of articles, and a couple of years of saying "If you're
going to write OO code, at least pretend to support objects", I'm not sure if
it's working.
I think we've hit the same problem/limit with Module::Install. The
assumption that authors will update/repair their code within a 5 year
transition period is not valid it seems, even with strong education.
At the moment, I'm working around the specific case of TT by local'ly
disabling warnings globally before calling TT methods, and trying to
restrain myself from using my co-maint to just add a dependency on
Params::Util and fix it.
As for the toolchain problem I plan to just knuckle down, kick some
heads, and fix the toolchain properly between 5.10.0 and 5.10.1. Mostly
these fixes will look like very small things. The first is the addition
of CPANPLUS_IS_EXECUTING from last week.
This will hopefully clear up the Module::Build bootstrap problem and
remote the need for Module::Install altogether (other than as syntactic
sugar).
Adam K
