Re: [Opensync-devel] [osynctool] osynctool_list_formats and other functions

[Daniel G. <go...@b1...>]

On Wednesday 28 October 2009 10:21:42 pm Henrik /KaarPoSoft wrote:
> In my opinion there is no relation between trace and return values.

Right, there isn't any.

> 
> Any function which has anything interesting to say should osync_trace.

But this only counts for OpenSync API code ...  you can use what ever you want 
in your OpenSync based application (e.g. osynctool, ...)

You don't have to use osync_trace() in your plugin ... but most OpenSync 
developer or used to osync-trace files already ... (even if no one knows why 
they have those strange file names and why there are soooo many of them ;))

> 
> Any function which could "fail" should
> (1) either return an osync_bool or a pointer which could be checked for 
> NULL.
> (2) have an OSyncError parameter
> (3) set the OSyncError in case it returns false or NULL.
> 

This counts only for OpenSync API ... we don't care about coding style outside 
of the OpenSync API. But i recommend that all OpenSync based application 
should take care about function which could fail and provide a OSyncError**

Best Regards,
Daniel

-- 
Daniel Gollub                        Geschaeftsfuehrer: Ralph Dehner
FOSS Developer                       Unternehmenssitz:  Vohburg
B1 Systems GmbH                      Amtsgericht:       Ingolstadt
Mobil: +49-(0)-160 47 73 970         Handelsregister:   HRB 3537
EMail: go...@b1...          http://www.b1-systems.de

Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg
http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D