Re: magic_quotes and the question of BC
| From: | Philip Olson | Date: | Mon, 25 Feb 2008 01:38:18 +0000 |
| Subject: | Re: magic_quotes and the question of BC | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-35777@lists.php.net to get a copy of this message | ||
On Feb 8, 2008, at 8:46 AM, Pierre Joye wrote:
On Feb 8, 2008 5:38 PM, Gregory Beaver <greg@chiaraquartet.net> wrote:The change here is to remove magical quotes and then have these functions always return 0, so yes we can change and keep [some] BC in one smooth motion.Frankly, I don't see why there is any vote whatsoever. It's plain stupid to consider removing them when a fully backwards-compatible solution exists that has no performance penalty, no security penalty, and in fact no penalty at all.It is not plain stupid to remove something when the underlying features do not exist. It is expected. Talking about BC in this case is a closed to be a complete non sense. For two reasons: 1. If can't do that between two major versions, let define a rule: we can't change _anything_ in PHP, no matter when (think: roll back all these fatal errors)
2. it is fixable in three lines (with braces). PEAR had much harder issues already, you can document the upgrade process (upgrade pear then php, make install will work if you include a full upgrading solution in go-pear.phar, if it is not the case already)But the general problem is with old code working in PHP 6, not new or updated code working in PHP 6. These functions should remain, and if not, then PHP 6 should break everything... meaning, be the "make PHP do what we want it to do with little BC in mind" instead of only doing that sometimes. Which is it? What is the PHP 6 mission statement? Regards, Philip