[interfacekit] Re: An idea

Exactly.  We'll get two benefits from it:  first, we'll be making
explicit what is already there implicitely, namely that some classes
need more priviledged access than others.  Second, we'll insulate those
classes from implementation changes in the target class.  If BWindow
only had one or two friends, I'd be for letting it go, but with this
many, there is a clear need for an additional interface.

e

DarkWyrm wrote:
> 
> >
> >Why generate a whole new layer between each class? By doing so we will
> >have twice the number of classes in the current InterfaceKit and 50% of
> >them will be merely pointing back to an original class' functionality.
> Actually, the idea isn't *every* class. If you look at, say, the BWindow
> class has *9* other classes which are defined as friends. While I know that
> they need access as such, having proxy classes is better OOP. They're not
> very big. Think of them as more like a BWindowAccessor class.
> 
> --DW

Other related posts: