--- Kurt Starsinic <[EMAIL PROTECTED]> wrote: > > Or, since it's overriding UNIVERSAL, > > > > UNIVERSAL::can::strict
It's overridding UNIVERSAL::can (via inheritance). It's not replacing it. If you want to use this module for your module, you have the new can() method. Other modules are unaffected. Perhaps the docs are not clear in that respect. > How about UNIVERSAL::should? The UNIVERSAL:: namespace is not appropriate as I'm not doing anything there. Still, I hate the name "strict::can" (I think I mentioned that before but it was buried at the bottom of an email). I do like "should", though. Class::Should? Ugh. That doesn't quite fit either. Cheers, Ovid -- If this message is a response to a question on a mailing list, please send follow up questions to the list. Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
