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 => []; # Use none of them. Yes, I realize that not putting attr4 in there at all is the same (default) thing. It's just kind of a semantic thing in my mind. But maybe It's just *my* mind. ;-) Thanks, David
- Re: RFC 193 (v1) Objects : Core support for method deleg... Michael G Schwern
- Re: RFC 193 (v1) Objects : Core support for method deleg... Piers Cawley
- Re: RFC 193 (v1) Objects : Core support for method deleg... Graham Barr
- Re: RFC 193 (v1) Objects : Core support for method deleg... David E. Wheeler
- Re: RFC 193 (v1) Objects : Core support for method deleg... Damian Conway
- Re: RFC 193 (v1) Objects : Core support for method deleg... Damian Conway
- Re: RFC 193 (v1) Objects : Core support for method ... Nathan Wiger
- Re: RFC 193 (v1) Objects : Core support for method ... David E. Wheeler
- Re: RFC 193 (v1) Objects : Core support for method ... Damian Conway
- Re: RFC 193 (v1) Objects : Core support for met... David E. Wheeler
- Re: RFC 193 (v1) Objects : Core support for... David L. Nicol
- Re: RFC 193 (v1) Objects : Core support... David E. Wheeler
- Re: RFC 193 (v1) Objects : Core support... Damian Conway
- Re: RFC 193 (v1) Objects : Core support for met... Damian Conway
- Re: RFC 193 (v1) Objects : Core support for method deleg... Damian Conway
- Re: RFC 193 (v1) Objects : Core support for method ... David E. Wheeler