« Return to Thread: [trunk] Last API Changes for 0.3x/0.40 / close to a freeze...

Re: [trunk] Last API Changes for 0.3x/0.40 / close to a freeze...

by Bjšoern Ricks-2 :: Rate this Message:

Reply to Author | View in Thread

Chris Frey schrieb:

> 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
>
>  
Thanks for giving me this hint. I completely forgot to check existing
functions which already returned an OSyncList. Today I changed
(hopefully) all list functions to return a copy of the internal list.

Bjoern

------------------------------------------------------------------------------
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

 « Return to Thread: [trunk] Last API Changes for 0.3x/0.40 / close to a freeze...