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

List:       kde-core-devel
Subject:    Re: about private 'd' pointer
From:       Falk Brettschneider <gigafalk () yahoo ! com>
Date:       2000-08-31 11:43:48
[Download RAW message or body]

Hi,

Simon Hausmann wrote:
> 
> > What about methods? Is the private d pointer intended to have methods
> > that should be hidden to the outside world?
> 
> Well, that's up to you :-) If a certain method which you would normally make
> private for example needs to be "protected" even more, then you can surely put it into
> a "private d pointer" . It's probably a matter of taste.
> 
> Methods being declared private in a class can still be accessed using #define private public
> hacks. But thinking about/using such hacks usually tells one that there is something wrong with
> the application/library design ;-) .
My purpose is simple:
I want to create a class that has got the public interface methods,
only.
All stuff used internally (internal maps, lists and their access
methods, internal mechanisms and helper methods) should be moved to that
'private d pointer' class.
So there's a good separation.

Last but not least the lists of methods in the class view of KDevelop
get smaller in the interesting classes! ;-))

Bye,
  F@lk

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

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