It's possible that we could do the following:
1) All subs (and methods) are considered multi 'under-the-hood'.
2) If the first declaration is explicitly 'multi', then you (or
others) can provide additional overloads (using 'multi') that won't
trigger warnings.
3) If the first declaration /doesn'
On Wed, Jul 06, 2005 at 12:58:44 +0100, Piers Cawley wrote:
> Then write yourself a module, call it 'multiplicity' say, which would allow
> you
> to say
>
> use multiplicity;
>
> sub foo (...) {...} # foo is a multimethod, even if there's already a
> 'SMD'
> #
Yuval Kogman <[EMAIL PROTECTED]> writes:
> On Fri, Jul 01, 2005 at 13:42:34 +1200, Sam Vilain wrote:
>> Yuval Kogman wrote:
>> >As I understand it SMD is now not much more than a mechanism to
>> >place a constraint on the MMD, saying that there can only be one
>> >method or subroutine with the sam
On Fri, Jul 01, 2005 at 13:42:34 +1200, Sam Vilain wrote:
> Yuval Kogman wrote:
> >As I understand it SMD is now not much more than a mechanism to
> >place a constraint on the MMD, saying that there can only be one
> >method or subroutine with the same short name.
> >Why is this the default?
>
> O
Yuval Kogman wrote:
As I understand it SMD is now not much more than a mechanism to
place a constraint on the MMD, saying that there can only be one
method or subroutine with the same short name.
Why is this the default?
Otherwise you lose this quite useful warning if the signatures didn't
matc
