in reply to Re^6: When C<use Module;> *not* the same as C<require Module; import Module;>?
in thread When C<use Module;> *not* the same as C<require Module; import Module;>?

Test code should not itself impose additional runtime constraints and requirements.

I'm having a difficult time reconciling the notion of a library that provides additional behavior yet does not impose any additional constraints or requirements. Please do consider writing up your views more formally; I'm genuinely curious as to what you do mean.

  • Comment on Re^7: When C<use Module;> *not* the same as C<require Module; import Module;>?

In Section Seekers of Perl Wisdom