Re: RFC 189 (v1) Objects : Hierarchical calls to initializers and destructors

   > I'm still not totally convinced that its so horrid to make the
   > File::LockAndKey DESTROY call $self->SUPER::DESTROY manually...
   
Believe me, it is in a large, deep, and/or MI hierarchy!


   > but it does break encapsulation.

Exactly.


   > If you can figure a way out of the dilema I proposed above, I suppose
   > this makes sense.

Easy. Don't let File::Lock::Mac inherit from File::Lock. Have it *delegate*
to File::Lock instead. See my forthcoming C<use delegation> RFC.

Damian