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

List:       kde-core-devel
Subject:    Re: private slots
From:       Olivier Goffart <ogoffart () kde ! org>
Date:       2007-01-03 15:46:06
Message-ID: 200701031646.11572.ogoffart () kde ! org
[Download RAW message or body]


Le mercredi 3 janvier 2007 16:05, Simon Hausmann a écrit  :
[...]
> And of course in general I suggest not to have any private methods in our
> public API at all. Putting it into your d-pointer gives you more
> flexibility in the future to change the implementation. There is really no
> good reason for exporting private functions.

From http://developer.kde.org/documentation/other/binarycompatibility.html

You can ... remove private non-virtual functions if they are not called by any 
inline functions.

So this still give us the possibility to change the implementation.

I think that choosing to have private member in the class itself or in the 
Private class is a matter of preference and choice.

Anyway, if that document is wrong, then, yes, we must do that in all our 
classes (and correct the document).

-- 
Gof

[Attachment #3 (application/pgp-signature)]

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