Re: Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.c zend_hash.c zend_hash.h zend_list.c zend_list.h
| From: | Zeev Suraski | Date: | Thu, 02 Aug 2001 17:42:29 +0000 |
| Subject: | Re: Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.c zend_hash.c zend_hash.h zend_list.c zend_list.h | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-61861@lists.php.net to get a copy of this message | ||
Yes, I was counting those too... It's still not a very large number (probably in the range of dozens, or hundreds at the most, compared to hundreds of thousands of users).
Both binary and source compatibility will have good warnings for developers and users (binaries will not load, source will not compile...), so there should be no real obscure-crashes type of problems.
I don't know, it seems to me that bumping a version number because of an API change which is transparent to end users is a bit odd, but if most people think otherwise, it's very much possible...
Zeev
At 10:36 02/08/2001, George Schlossnagle wrote:
Andi and I are in Redmond right now, so we're kinda busy with different things... My personal view is that: - If a major (well, sub-major) version bump was required, it's really no biggy - For this case, I don't think it's required, since the heads-up is only for developers of PHP extensions, which are not that many. For others, it may be a bit obscure on why the heck we bumped the version number. I would submit that it's also a heads-up to anyone who uses non-core 3rd party extensions as well, as they will no longer have binary or source compatibility.-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/