Re: [PHP4BETA] changing all "php3" to "php4" ?
| From: | Rasmus Lerdorf | Date: | Thu, 27 May 1999 18:08:20 +0000 |
| Subject: | Re: [PHP4BETA] changing all "php3" to "php4" ? | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-1137@lists.php.net to get a copy of this message | ||
> First, there isn't any point in supporting both versions since PHP4 is
> downwards compatible with PHP3. Before anybody comes back saying 'no way,
> it's not', my answer is that we'll release it only when this sentence is
> true. That's the whole point about PHP4, and the fact that you can't run
> both versions concurrently would sort of prove that point.
Well, there will be a transition phase. PHP4 is not going to be 100%
backward compatible. We have already identified things that just won't be
fixed. And second, PHP3 is stable. It will be a while before PHP4 is.
The lack of a transition phase where you don't have to bet the farm on
PHP4 will slow down the migration to PHP4. If it really is such a big job
to make them run concurrently, the transistion phase will have to be done
through cgi.
> Second, you can't do it. There are functions with no php3_ prefix that
> have changed (for example, getParameters(); there are many more) and it
> won't work anyway, as only one version will get linked. Since I don't
> consider it a good thing to run both versions concurrently, I don't want to
> even try sorting that problem out.
What do you mean only one version will get linked? Both PHP3 and PHP4
compile as DSO's. If it weren't for a couple of symbol clashes, both
could easily be loaded concurrently.
And besides, none of this is a reason not to change "php3" strings to
"php4" throughout the code even if it isn't for concurrency reasons.
-Rasmus
--
PHP 4 Beta