On Dec 4, 2005, at 4:11 PM, Ovid wrote:
Your world and my world can be considerably different. Using code very
similar to this solved a problem I had with Class::Trait whereby I was
exporting methods which should not have been exported. Also, if one is
routinely in the habit of checking
Ken Williams wrote:
The concern I have about the namespace is that the pragma 'strict'
suggests that when you use it, you must eliminate ambiguities in your
code so that the compiler doesn't have to guess what you mean. That's
not what you're doing here, you're erecting new rules to enforce
On 12/7/05, David Golden [EMAIL PROTECTED] wrote:
Ken Williams wrote:
The concern I have about the namespace is that the pragma 'strict'
suggests that when you use it, you must eliminate ambiguities in your
code so that the compiler doesn't have to guess what you mean. That's
not what
--- 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.
