Shared d-pointers

QT4 macros make it really easy to implement shared d-pointers. So i’m
going to go ahead and update a lot of the libavogadro code so that it
uses shared d_ptrs… specifically Q_DECLARE_PRIVATE(Class) and
ClassPrivate * const d_ptr.

This way when we move libavogadro over to Kalzium we don’t need to worry
about if we ever need to subclass anything in our library. I want to do
it now because of all the binary compatibility stuff. Just seems like a
good precaution.

-Donald

I think that’s a good idea! In case you find it useful, techbase.kde.org has
some documentation:

http://techbase.kde.org/Policies/Library_Code_Policy#D-Pointers

-Benoit

On Monday 23 April 2007 02:17:49 Donald Ephraim Curtis wrote:

QT4 macros make it really easy to implement shared d-pointers. So i’m
going to go ahead and update a lot of the libavogadro code so that it
uses shared d_ptrs… specifically Q_DECLARE_PRIVATE(Class) and
ClassPrivate * const d_ptr.

This way when we move libavogadro over to Kalzium we don’t need to worry
about if we ever need to subclass anything in our library. I want to do
it now because of all the binary compatibility stuff. Just seems like a
good precaution.

-Donald


This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/


Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-devel