Talk:Policies/Library Code Policy: Difference between revisions
No edit summary |
|||
| Line 3: | Line 3: | ||
: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) | :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) | ||
::Yay, but only, if it weren't locked or you have the necessary permissions. :-P | |||
::OTOH, I think, it's good, that I put my first thoughts here. The const'ness of the d-pointer prevents the default assignment of being used. --[[User:Nikolaus|nikolaus]] 12:47, 30 January 2007 (CET) | |||
Revision as of 11:47, 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)
- Yay, but only, if it weren't locked or you have the necessary permissions. :-P
- OTOH, I think, it's good, that I put my first thoughts here. The const'ness of the d-pointer prevents the default assignment of being used. --nikolaus 12:47, 30 January 2007 (CET)