Re: compat.h

[Doug MacEachern <do...@pobox.com>]

Jim Jagielski <ji...@jaguNET.com> wrote:

> Doug MacEachern wrote:
> > 
> > It's a bit ironic after all the blood, sweat and tears over namespace
> > cleanup that the name `compat.h' was chosen.  There's at least one os
> > that has a file with this name which is found in -I paths before
> > Apache's compat.h, which breaks mod_perl in a big way.  Could we move
> > the compat.h stuff to a new file called ap_compat.h or some such and
> > have the current compat.h just #include "ap_compat.h"??  Or should we
> > re-order the -I paths?  Other solutions?
> > 
> 
> I'm for the rename myself. Even makes sense :)

okay, so I guess we're at 2 +1's for this, if there is a third, I'm
afraid I'm not the right person for the job.  I'm guessing/hoping it
would take Ralf or somebody else who's familar with the compat stuff a
few minutes to take care of??

-Doug

Re: compat.h

[Rasmus Lerdorf <ra...@lerdorf.on.ca>]

> > I'm for the rename myself. Even makes sense :)
> 
> okay, so I guess we're at 2 +1's for this, if there is a third, I'm
> afraid I'm not the right person for the job.  I'm guessing/hoping it
> would take Ralf or somebody else who's familar with the compat stuff a
> few minutes to take care of??

I suppose it needs to be done.  A lot of modules out there will be
affected though.  It will break builds of at least mod_auth_mysql and
mod_php3.

-Rasmus