Re: RFC 193 (v1) Objects : Core support for method delegation

   >   PRL> One powerful application of delegation is as a replacement for
   >   PRL> inheritance where the internals of a prospective base class are
   >   PRL> inaccessible or inconvenient, or the base class was not designed
   >   PRL> to be inherited and yet it must be.
   > 
   > isn't this a HAS_A type of relationship?
   
Yep.


   > i have plenty of these in my new project and it is a pain.

Yep. Hence this RFC.


   >   PRL>         use Class::Delegation
   > 
   > shouldn't that be use delegation? i think you have a cut and paste
   > error.

You're correct. Many thanks.
(That's what I get for pre-testing all the code in my RFCs! ;-)

   
  
   >   PRL>                 in  => [qw( getline getlines getc ungetc eof read sysread
   >   PRL>                            input_record_separator input_line_number )],
   > 
   > what about a way of delegating ALL the methods of an object? any way to
   > signify that?
   > 
   > 	in => 'ALL',
   >
   > will look up all current methods (maybe tagged?) from the class 'in' and
   > handle that. then you don't have to update all the delegation calls each
   > time the 'in' object changes.

Specifying C<in => []> does that. See the description of "catch-alls"
below the bit you've quoted.


Damian