in reply to Re^5: Tutorial: Introduction to Object-Oriented Programming
in thread Tutorial: Introduction to Object-Oriented Programming

Maybe I'm missing something with your implementation but wouldn't something like:
package Rover; #a class of it's own ;) sub get_set_color { my $self = shift; if( @_ ){ $self->oo_set( 'color' , $_[0] ); } else { $self->oo_get( 'colour' ); } }
lead to the same problem that Abigail-II was talking about in the first place?

rdfield

Replies are listed 'Best First'.
Re: Re: Re^5: Tutorial: Introduction to Object-Oriented Programming
by fruiture (Curate) on Dec 18, 2002 at 13:45 UTC

    Well, as long as you base such a thing upon a hash (and a variable solution like the Superclass must use a hash), you cannot avoid that, but it's limited to a few lines of accessor method code. I don't think it's productive to assume a typo wherever possible and to make it impossible to break things.

    This cannot happen when you create an accessor method automatically.

    --
    http://fruiture.de