Re: [RFC] Versioning rules for PHP/Zend/PEAR/Extensions
| From: | Andi Gutmans | Date: | Wed, 26 Sep 2001 15:24:25 +0000 |
| Subject: | Re: [RFC] Versioning rules for PHP/Zend/PEAR/Extensions | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-66660@lists.php.net to get a copy of this message | ||
At 12:01 PM 9/26/2001 -0400, Joao Prado Maia wrote:
On Wed, 26 Sep 2001, Andi Gutmans wrote: I think the key still lies in creating a repository for C extensions where each extension can have its own release cycle. That is also true, but we still need a reliable way to check for the version of specific extensions. Having just bumped into an inconsistency between GD 1.6.2 and GD 2.01 output, this would help a lot. However, the problem is already out there and to create code that is truly portable I couldn't rely on even this new (if it ever comes to life) feature. This sort of thing really complicates writing portable code. not just for different platforms but also for different versions of extensions. Just a repository wouldn't help much from the programmer's perspective IMHO, if the current situation continues.I agree completely. We need a way to check what version each extension is. We have broken BC quite a bit in 4.0.7 so maybe we should add this to 4.0.7 so that we can get this whole external C extension thing going ASAP? Andi