On Tuesday 29 November 2005 17:29, Colm MacCarthaigh wrote: > On Tue, Nov 29, 2005 at 05:25:31PM +0000, Nick Kew wrote: > > On Tuesday 29 November 2005 16:37, [EMAIL PROTECTED] wrote: > > > -AP_DECLARE(void) ap_dbd_prepare(server_rec *s, const char *query, > > > +DBD_DECLARE(void) ap_dbd_prepare(server_rec *s, const char *query, > > > const char *label) > > > > OK, other modules do this. Yet the #defines for DBD_DECLARE et al > > are identical to AP_DECLARE, aren't they? What is supposed to be > > the purpose of namespacing different modules? > > In mod_dbd.dsp we can now have "/D DBD_DECLARE_EXPORT" which means we > use dllexport, not dllimport without over-riding other AP_DECLARE's :-)
Aha! Thanks for the explanation [fx: mutters about the lengths Windows will go to to introduce nonstandard features that make life difficult]. I guess that must be the same reasoning that drives people to declare different 'preprocessor namespaces' in the LINK argument to APR_DECLARE_EXTERNAL_HOOK and friends. Is mod_authz_dbd going to have the same kind of problem using AP? -- Nick Kew
