Re: zend module patch

> We already broke the API numerous times in 4.0.7. The thing we didn't > break is the narrow binary compatibility of the module_entry structure. We did not break this particular API and there is technically no reason to introduce this particular change at this time. We can easily support two different structures in the future. The glue code is as simple as a couple of casts and a check for a magic value. And yes, I volunteer for taking the burden of implementing it upon me. Am I the only one who values stable APIs? There is no simple way to build a PHP extension which works across multiple PHP versions which makes those people and companies who develop extensions quite unhappy. If we want to draw in wider support from a larger audience we should start to actually care about building something more reliable. > In my opinion, we should incorporate the changes in the next release of > PHP. We can perhaps restart the whole 4.0.7 release process, or just force > a couple of more RC's. Andi even suggested the possibility of skipping > 4.0.7 and going directly to 4.0.8, but that's mostly semantics... Again, let us release 4.0.7 as it is and let us get the extended module structure right for the release afterwards. Consider 4.0.7 as a bugfix version of 4.0.6 if you want. - Sascha Experience IRCG http://schumann.cx/ http://schumann.cx/ircg