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 the other module has changed in an incompatible way. What's a
> good way of doing this?
What's wrong with just sticking your test at the end of the module? Any
code found "lying around" in the module will be run as soon as the
module is compiled. This is useful for initialising the module, or
possibly testing it ....
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
