Luke Palmer wrote:
Joe Gottman writes:
----- Original Message ----- From: "Jonathan Lang" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, December 20, 2003 3:41 PM
Subject: [perl] Re: Object Order of Precedence (Was: Vocabulary)
Larry Wall wrote:
If DangerousPet doesn't define a feed method at all, then we might dispatch to Pet and Predator as if their methods had an implicit "multi".
And the C<default> trait is the tie-breaker when several options are equally likely candidates (in terms of type information); OK.
I'm a little leery about calling this trait "default". The problem is that we are already using "default" as a keyword (see the switch statement), and having a trait with the same name as a keyword might confuse users and/or the compiler.
Perl's using a top-down compiler now, so it won't be looking for the keyword variant of C<default> after "is". "default" is sufficiently overloaded in English, and by context in Perl, that I don't think anyone will get confused.
Not to say that other names for this trait aren't welcome.
C<preferred>
