Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Re: Re: Re: Why breaking can() is acceptable

by TimToady (Parson)
on Apr 07, 2004 at 02:12 UTC ( #343172=note: print w/ replies, xml ) Need Help??

in reply to Re: Re: Why breaking can() is acceptable
in thread Why breaking can() is acceptable

Yes, you can always call "next METHOD" to pass the buck to the next method in the list of candidates. Though an AUTOLOAD is going to be pretty far down the pecking order, because Perl will prefer all declared methods over all wildcard methods, and autoloading is one form of wildcarding. So only an AUTOLOAD in a parent class (or a sibling class, since these are "next" semantics) is possible in the remaining list of candidates.

Though as for get_* and set_* methods, those would be non-standard in Perl 6. Perl's accessor methods will not be split into get and set methods. Rather, they'll be single methods that are lvaluable if you want to allow setting.

Comment on Re: Re: Re: Why breaking can() is acceptable

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://343172]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (2)
As of 2015-11-27 20:28 GMT
Find Nodes?
    Voting Booth?

    What would be the most significant thing to happen if a rope (or wire) tied the Earth and the Moon together?

    Results (731 votes), past polls