Re: osx changes
| From: | Stig Sæther Bakken | Date: | Wed, 21 Apr 1999 21:53:16 +0000 |
| Subject: | Re: osx changes | ||
| References: | 1 2 3 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-5186@lists.php.net to get a copy of this message | ||
Chad Cunningham wrote:
>
> Stig Sæther Bakken wrote:
>
> > This conflict should normally not occur because both PHP and Apache
> > would define HAVE_SNPRINTF to the same value. If they try setting it to
> > different values, you have a fishy setup (either in Apache or with a
> > stale config.cache file in PHP).
> >
> > - Stig
>
> Thanks, looks like I overlooked the obvious... Apache defines it for rhapsody
> as #define HAVE_SNPRINTF, whereas php's configure defines it as #define
> HAVE_SNPRINTF 1. I guess the compiler is anal...
Oops, of course. PHP has grown a "tradition" of setting HAVE_XXX macros
to 1 or 0 and using #if instead of #ifdef/#ifndef. Most other packages,
including Apache apparently, use #ifdef/#ifndef for such macros.
The reason is historical[1], and there is really no reason to do it this
way anymore. If this causes you problems, we can at least change
HAVE_SNPRINTF to defined/undefined instead of 1/0 so it is consistent
with Apache and default autoconf behaviour.
- Stig
[1]: If memory serves me it was used in the function list in early 3.0
alpha versions, before the module API was developed, to determine
whether a function should be included in the function names hash.
--
PHP Development Mailing List http://www.php.net/
To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net
For help: php-dev-help@lists.php.net