On Wed, Aug 22, 2007 at 01:03:47AM +0200, Julien Kerihuel wrote: > On Wed, 2007-08-22 at 00:34 +0930, Dan Shearer wrote: > > A libmapi client does this: > > > > #include <libmapi/libmapi.h> > > #include <stdio.h> > > : > > > > If instead you do this: > > > > #include <stdio.h> > > #include <libmapi/libmapi.h> > > : > > libmapi client are not required to include stdio.h since it is already > included within libmapi/libmapi.h.
I was just using stdio as an example, as explained in the last email, to illustrate that currently libmapi wants to be the first #include at least with anything I tried (???) But this brings up another point: libmapi users can't be expected to care about libmapi. Code that includes libmapi.h must be assumed to have just about anything in it, so comments about whether libmapi does or does not have stdio are beside the point. >From the point of view of the user, libmapi is exclusively about sending MAPI packets on the wire and anything else it does is a potential conflict and a bug. -- Dan Shearer [EMAIL PROTECTED] _______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
