Re: [PHP4BETA] Running PHP3 and PHP4
| From: | Sascha Schumann | Date: | Tue, 07 Sep 1999 21:09:21 +0000 |
| Subject: | Re: [PHP4BETA] Running PHP3 and PHP4 | ||
| References: | 1 2 3 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-4217@lists.php.net to get a copy of this message | ||
On Tue, Sep 07, 1999 at 10:58:07PM +0200, Zeev Suraski wrote:
> At 18:06 07/09/1999 , Stig Bakken wrote:
> >On Tue, 7 Sep 1999, Sascha Schumann wrote:
> >
> >| On Tue, Sep 07, 1999 at 05:09:27PM +0200, Stig Bakken wrote:
> >| > On Tue, 7 Sep 1999, Andrey Zmievski wrote:
> >| >
> >| > | Is there a way to set up both PHP3 and PHP4 to run as Apache modules
> >| > | on the same server?
> >| >
> >| > Only if you find and rename all functions in php4 with the same name but
> >| > different return value/arguments than the same function in php3.
> >|
> >| I think this is called "versioning." Sun has used it for
> >| years in their libraries and GNU libc 2.1 uses it by default
> >| as well.
> >
> >I seriously think we should make it possible for users to link with both
> >php3 and php4, especially when it is more or less just a matter of adding
> >a few defines to php3_compat.h.
>
> It isn't. PHP 3.0 and 4.0 modules may interfere with each other; Finding
> and changing the names of all of the API functions is very annoying task,
> and isn't something we want to do generally (why rename the API?), etc.
You assume that it requires explicit action involving massive
code changes. If this would be the case, I also wouldn't
encourage it.
I don't know exactly how versioning works in i.e. the C
library, but I do know that it's completely transparent to
users and developers.
I see this as a benefit - if it's easy to realize and it
doesn't interfere with other parts because of technical
reasons, there is hardly any chance of doing something wrong.
--
Regards,
Sascha Schumann
Consultant