> not entirely true, actually, because if we used pointers for KSpreadValue
> then the private pointer inside of KSpreadValue would not be needed to
> achieve sharing.  The private data itself would be in KSpreadValue.  So it
> ends up being the same size.
Yes, I was wrong before.

> However I would still support your way of doing it which allows us to use
> the constructor/destructor/copy constructor to keep a reference count and
> so we know when to delete the data.  (if you think about it, KSpreadValue
> is nothing more than a really fancy pointer to KSpreadValueData).
Another advantage is that refcounted object like is easier and safer to handle 
than plain pointer. But maybe it's just me....


_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel