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?

> 
> Bye,
>  Simon
Thanks a lot,
  F@lk

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com