Difference between revisions of "Talk:Policies/Library Code Policy"

Jump to: navigation, search
m (D Pointers)
Line 1: Line 1:
 
== D Pointers ==
 
== D Pointers ==
 
It should be mentioned, that when using d-pointers, the copy constructor and assignment operator either have to be implemented correctly or they have to be forbidden. The implicit copy constructor and assignment operator copy just the value of the pointer. The pointer to the former Private data will get lost (memory leakage).
 
It should be mentioned, that when using d-pointers, the copy constructor and assignment operator either have to be implemented correctly or they have to be forbidden. The implicit copy constructor and assignment operator copy just the value of the pointer. The pointer to the former Private data will get lost (memory leakage).
 +
 +
:I hate to point out the obvious, but this is a wiki and you can add this information yourself as easily as comment on it. =) --[[User:Aseigo|Aseigo]] 00:49, 30 January 2007 (CET)

Revision as of 00:49, 30 January 2007

D Pointers

It should be mentioned, that when using d-pointers, the copy constructor and assignment operator either have to be implemented correctly or they have to be forbidden. The implicit copy constructor and assignment operator copy just the value of the pointer. The pointer to the former Private data will get lost (memory leakage).

I hate to point out the obvious, but this is a wiki and you can add this information yourself as easily as comment on it. =) --Aseigo 00:49, 30 January 2007 (CET)

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal