On Sat, 2007-08-18 at 05:24 +0930, Dan Shearer wrote: > mapidump_* are useful: if global_mapi_ctx->dumpdata is non-zero then > data and objects are printed on stdout. I agree this isn't a job for > DEBUG. > However implementors using various OSs and widget toolkits often won't > have a stdout. How about allowing other mechanisms to help these people? > It is very easy to allow the user to supply an alternative file/socket.
I introduced mapidump functions for debugging only (x86), but it seems like they were quite useful for other developers/implementors. We can obviously provide additional file/socket mechanism. It shouldn't be long and we can use the global context to set and use it transparently within mapidump functions. This way we won't break the existing API. > When OpenChange is more mature this facility is probably something that > is disabled by default for security reasons, right? For dump-data, yeah certainly. At some point I suppose we will replace this global data structure field with #if DEBUG directives and offer this option at build time only. For the moment it is still quite useful when searching why mapi calls returned MAPI_E_CALL_FAILED. Julien. -- 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
