MAPI_RETVAL_IF was introduced for convenience and has been extended to tools while it should had been kept within libmapi code only - It is anyway located in public header files.
Maybe should we consider adding a set of defines and macros for developer usage. In the same order of idea (need to read your other devel emails), working on the DEBUG mode sounds quite an issue we should fix quickly. Julien. On Fri, 2007-08-17 at 09:14 +0930, Dan Shearer wrote: > Should MAPI_RETVAL_IF be encouraged in user, as in utils/*c ? Shouldn't > it be kept private to libmapi? > > Not only does it potentially break applications if the libmapi > definition changes, but it stops users from adding their own > errorhandling because it has a return() in it. So if I want to include > debugging error messages that indicate the libmapi routine that failed, > I can't. > -- Julien Kerihuel [EMAIL PROTECTED] OpenChange Project Manager GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
