Re^4: Class::InsideOut - yet another riff on inside out objects.

[adrianh]

Isn't that going to be done by that class's DESTROY method? That is, the "next" call will do it.

No. The NEXT is there in case we have inherited from another non-inside-out class that has its own DESTROY method.

The idea is that all of the sub-classes of Class::InsideOut can now avoid writing custom DESTROY methods since the base-class handles it for them.

Hopefully this makes some vague sort of sense :-)

[John M. Dlugosz]

Hmm, if the instance held a list of all valid attributes, then you would not need to search all attributes for all classes.

[adrianh]

True, but this list is impossible to determine at compile time since you can change an objects class with bless at any time.

In theory you could replace bless with a custom version that tracked the object through it's class changes - but this is really just an optimisation - and it's a little early in the day for that :-)