Further to Athanasius's comments above:
My understanding is that the object's innards should stay inside the object.
But they can't stay inside forever. After all, an object's innards are data, and data must be accessed and sometimes even (gasp) changed in order to be useful. Consider the 'name' attribute in the example code of the OP. It has no getter/setter method. Except by direct reading or writing via the object reference, which we all agree is a Really Bad Idea and which no one will ever do, this data cannot be accessed in any way. What good is it? Of course, you can imagine you might write another method that would access it, say along the lines of
sub string_of {
my $self = shift;
return "$self->{color} $self->{name}";
}
sub print {
my $self = shift;
printf "I am a %s \n", $self->string_of;
}
Both these methods "expose" object attributes to application code without any risk that they may be changed, and why not? It's up to the library (or class) programmer to decide to offer such methods or not.
Give a man a fish: <%-{-{-{-<