>> anyway, in the end I guess I wouldn't suggest moving to T::M entirely >> just >> yet. but if you want to use it occasionally within certain tests I think >> that's fine. > > > Of course another alternative is to bundle a sufficient version of T::M > under t/.
that's an idea. so long as it's not installed with 'make install'. or indexed by cpan either, I suppose. >> yeah, that's the issue for me - t_cmp() prints out too much cruft when >> everything is just fine. > > > agreed, and we could certainly change that to match T::M's behavior, > *but* I still want to be able to force it to print the verbose output > even when everything is fine. yeah, that's a good idea. > I prefer to first see the output and then write the comparison test than > the other way around. I don't understand why T::M doesn't allow an > option to force the verbose output. I dunno the politics here, but it might make for a nice enhancement. I'll look into it. --Geoff
