On Thu, Apr 09, 2009 at 09:30:16AM +0200, Bjoern Ricks wrote:
> >> [API] Common API interface pattern for list-implementations
> >>
http://www.opensync.org/ticket/975> >>
> >> Bj?rn is working on that.
> >>
> >
> > still ongoing - expected to be complete soon.
> >
> Done and committed in r5448. Now all list related interface will return
> a OSyncList. The returned OSyncList is always a shallow copy of an
> internal opensync structure/list and has to be freed in the application
> or plugin. Please be sure that osync_list_free is called on the returned
> list to avoid memory leaks.
I'm assuming that not all functions that return a OSyncList* behave
this way? For example, osync_plugin_resource_get_objformat_sinks().
(This could very well be my API ignorance showing) :-)
- Chris
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
