[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: about private 'd' pointer
From:       Peter Putzer <pputzer () edu ! uni-klu ! ac ! at>
Date:       2000-08-31 8:35:04
[Download RAW message or body]

On Thu, 31 Aug 2000, Falk Brettschneider wrote:

> Hi,
> 
> Simon Hausmann wrote:
> > 
> > 
> > Well, the point about that d is exactly to be private! If you make it protected
> > and let inheritting classes access is, then adding/removing variables to/from the
> > structure breaks binary compatibility. (obviously)
> > (which makes the idea of the "d" void :)
> > 
> > So I think what you want are simple protected member variables. Just keep in mind
> > that these are fixed then, meaning adding/removing/changing them breaks binary compatibility.
> > But that's the price for the advantage of them being shared / available for inheritting classes.
> Hmm...right. :)
> What about methods? Is the private d pointer intended to have methods
> that should be hidden to the outside world?

Not really, but sometimes you may want to have some (constructors and
destructors most likely)

Peter

[prev in list] [next in list] [prev in thread] [next in thread]