Damian Conway wrote:
Err, that *is* the default behaviour. Delegation doesn't occur unless
you specify it. Or am I missing your meaning here?
use delegation
attr1 = [qw( method1 method2 method3 )],
attr2 = [qw( method4 method5 )],
attr3 = __ALL__, # Use all of them.
attr4 =
Damian Conway wrote:
It was (and is) a good suggestion. I suspect however that it should be
attr3 = [__ALL__]
so that classes can still have an CALL method delegated.
(Yes, now they can't have an C__ALL__ method,
but maybe that's a Good Thing ;-)
Agreed. Yes, that's very good,
"David L. Nicol" wrote:
When you want to turn off an inherited delegation in an ISA situation?
Um, I don't think I understand the question. Delegation is not
inherited. Any module you inherit from you won't use for delegation,
AFAIK. They're two different beasts.
Or am I misunderstanding
Perl6 RFC Librarian wrote:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Core support for method delegation
This idea rocks, Damian! I want it now! Just one suggestion, however...
The proposed delegation mechanism would work via a
On 1 Sep 2000, Perl6 RFC Librarian wrote:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Private keys and methods
Here, here amen, Damian! This one gets my instant vote!
David
On Sat, 2 Sep 2000, Nick Ing-Simmons wrote:
Damian Conway [EMAIL PROTECTED] writes:
But I agree that anything beyond that is simply horrible. You'll only
drive more people *away* from OO, because it generates so horribly
inefficient code. If you want a constructor called, than
Michael Fowler wrote:
On Fri, Sep 01, 2000 at 11:41:47AM -0700, David E. Wheeler wrote:
Michael Fowler wrote:
my Dog $spot; # $spot is now a blessed Dog object
$spot-name("Fido");# $spot-{'name'} eq "Fido"
print ref $spot
