Re: camel_store_get_folder_info() memory handling

CamelStore::free_folder_info()'s v.method can be overridden, so it's
really up to your CamelStore implementation.

The consumer of the ::get_folder_info() API is supposed to
call ::free_folder_info(), but since it can be overridden - you can make
it noop, free the info, or free some subset of the info (e.g. it could
free the structs but not the strings or some such if the strings point
to some internal memory).

There are at least 2 convenience implementations in camel-store.h, one
is a noop and one is a free-all type.

Hope that helps,

Jeff

On Wed, 2006-02-15 at 14:21 +0100, Jules Colding wrote:
> Hi,
> 
> Please correct me if I am wrong, but I have suddenly become in doubt
> about who "owns" the memory returned by camel_store_get_folder_info().
> 
> camel_store_get_folder_info() returns a CamelFolderInfo* so the memory
> pointed returned by my provider implementation of get_folder_info() must
> be freed by the caller. Is that correct?
> 
> 
> Thanks,
>   jules
> 
> 
> 
> _______________________________________________
> Evolution-hackers mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/evolution-hackers
>