Got this question forwarded on to me. Hope the talk of .t files
doesn't go over everyone's heads.
On Tue, Jun 26, 2001 at 03:40:06AM -0500, Me wrote:
> > I'm writing a package that uses another module. This latter module may
> > change somewhat erratically and unreliably, outside of my control.
On Tue, Jun 26, 2001 at 12:17:50PM -0400, Richard J. Barbalace wrote:
> Trying to do this gives a warning. For example:
> package MyPackage;
> use Flakey;
> .
> package MyPackage::A;
> .
> package MyPackage::C;
> # Test if Flakey is compatible with MyPa
> On Mon, Jun 25, 2001 at 06:13:18PM -0400, Richard J. Barbalace wrote:
>
> > I'm writing a package that uses another module. This latter module may
> > change somewhat erratically and unreliably, outside of my control. As
> > a result, I want to have the package test itself and die if it notic
On Mon, Jun 25, 2001 at 06:13:18PM -0400, Richard J. Barbalace wrote:
> I'm writing a package that uses another module. This latter module may
> change somewhat erratically and unreliably, outside of my control. As
> a result, I want to have the package test itself and die if it notices
> that t
Hi.
I'm writing a package that uses another module. This latter module may
change somewhat erratically and unreliably, outside of my control. As
a result, I want to have the package test itself and die if it notices
that the other module has changed in an incompatible way. What's a
good way of
