Guenter Knauf wrote: > Hi, > Guenter Knauf schrieb: >> I would prefer to stay with the '#ifdef APR_VERSION < 2' because they >> cost us nothing, and at least at the moment it is possible to build >> httpd-2.2.x with APR 2.0.0-dev - just tested with NetWare, and >> absolutely no prob, compiles and runs. > Surprisingly I've just found that we still have apu_version.h + > apu_version() with APR-2.0.0-dev, and if we keep this in future then I > even see no reason to ifdef mod_info in trunk .... > > Bill, do we keep apu_version.h with APR-2.x, or will it be removed? > Maybe we can just: > #define APU_VERSION APR_VERSION > #define apu_version apr_version > > and have then a simple backward compat?
The issue is that 2.0 anticipates renaming all of the foo_ex functions back to foo, discarding the old, insufficient interfaces. Another round of name space review, normalizing inconsistent API's (why is the retval arg pointer not the first arg to function x?) and so forth. Provided that is how the apr members want to move forwards, consumers are likely to need to adjust their sources, meaning that dropping apu_version may be a benefit, flag that other changes are necessary. Anyways, this list to suggest this is [email protected], but it sounds like an idea worth considering, especially during the transition.
