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 you're doing here, you're erecting new rules to enforce API
> > boundaries between library and caller.
>
> "stricter::can" ?
>
> Or, since it's overriding UNIVERSAL,
>
> UNIVERSAL::can::strict
I think that Ken hit on the crux of my concern. Your nomenclature
suggests that you're eliminating ambiguities, and putting the word
"strict" or "stricter" anywhere in the namespace is central to this
confusion.
How about UNIVERSAL::should?
- Kurt
