> 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
- Re: RFC 189 (v1) Objects : Hierarchical calls t... Nathan Wiger
- Re: RFC 189 (v1) Objects : Hierarchical cal... John Siracusa
- Re: RFC 189 (v1) Objects : Hierarchical... Nathan Wiger
- Re: RFC 189 (v1) Objects : Hierarc... John Siracusa
- Re: RFC 189 (v1) Objects : Hie... Nathan Wiger
- Re: RFC 189 (v1) Objects : Hierarchical... Tom Christiansen
- Re: RFC 189 (v1) Objects : Hierarchical... Damian Conway
- Re: RFC 189 (v1) Objects : Hierarchical calls t... Mike Lambert
- Re: RFC 189 (v1) Objects : Hierarchical cal... Michael G Schwern
- Re: RFC 189 (v1) Objects : Hierarchical cal... Damian Conway
- Re: RFC 189 (v1) Objects : Hierarchical calls to in... Damian Conway
- Re: RFC 189 (v1) Objects : Hierarchical calls t... Michael G Schwern
- Re: RFC 189 (v1) Objects : Hierarchical calls to initial... Mike Lambert
- Re: RFC 189 (v1) Objects : Hierarchical calls to initial... John Tobey