[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-imaging
Subject:    [Kde-imaging] Ownership policy
From:       aurelien.gateau () free ! fr (Aurelien Gateau)
Date:       2004-04-09 0:56:34
Message-ID: 200404090054.39256.aurelien.gateau () free ! fr
[Download RAW message or body]

Hi!

I'm trying to write a real implementation of KIPI::Interface in Gwenview. I'm 
wondering about the ownership policy of currentAlbum() and 
currentSelection(): Should the caller be responsible of deleting it or should 
it be up to the KIPI::Interface implementation? If the second, what would be 
the lifetime of the returned pointer?
I personally would prefer to let the caller be responsible of it as it would 
simplify the code in the KIPI::Interface implementation and would avoid crash 
if the plugin access the ImageCollection after the host deleted it.

PS: I will be away on Sunday (11/4) till next Sunday (18/4). Just so that you 
don't wonder why I don't answer fast :-)

Aur?lien
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic