On February 23, 2014 11:15:47 AM David Faure wrote: > Add sharedConfig() accessor, to avoid manipulating a raw KConfig * as > returned by config(). > I had thought that when dealing with smart pointers, one should in general always pass around the smart pointer and not the raw pointer behind it. While you can reconstruct the smart pointer from the raw pointer here, there is still a point in time where you may lose access to the pointer if it goes out of scope elsewhere. Thus I'd like to deprecate/get rid of the raw pointer version of that function.
However, I understand the frameworks are seeking to maintain source compatibility as much as possible. I looked around on Techbase for some guidance, but I wasn't able to find any. If such documentation exists, could someone point me to it please? Otherwise, could some one outline it? -- Matthew
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
