2011/8/25 Albert Astals Cid <aa...@kde.org>: > The point is that usually you do not know what the library will end up doing > and by using d-pointers everywhere you make it easier for yourself to maintain > binary compatibility in the future.
But in the case that most classes won't grow in the future by using my strategy (keeping d-ptr NULL when possible) we cut down the number of memory allocations, and also simplify the existing code that doesn't work with the private class' data. So, I'm going to keep following the current strategy. -- Alexander Potashev
