> goes? Your logic suggests that I'd never want to meddle in the base's > implementation. What happens when the base classes' author finally fixes the problem you wrote around (and incidentally changes touchy implementation details in the base)? What happens someday when you can't see the implementation of the base class that you are inheriting from? Ack!!! =^) Matt
- Re: RFC 189 (v1) Objects : Hierarchical... Piers Cawley
- Re: RFC 189 (v1) Objects : Hierarc... Graham Barr
- Re: RFC 189 (v1) Objects : Hie... Nathan Wiger
- Re: RFC 189 (v1) Objects : Hie... Damian Conway
- Re: RFC 189 (v1) Objects : Hierarc... Damian Conway
- Re: RFC 189 (v1) Objects : Hierarchical cal... Tom Christiansen
- Re: RFC 189 (v1) Objects : Hierarchical... John Siracusa
- Re: RFC 189 (v1) Objects : Hierarchical calls to initial... Michael G Schwern
- Re: RFC 189 (v1) Objects : Hierarchical calls to initial... Damian Conway
- Re: RFC 189 (v1) Objects : Hierarchical calls to in... Michael G Schwern
- Re: RFC 189 (v1) Objects : Hierarchical calls t... Matt Youell
- 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 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