Re: 4.0.2 + 4.0.3p1 not binary compatible?

At 00:04 5/12/2000, Doug MacEachern wrote:

seems the change in zend_compile.h that moves `filename' from zend_op to zend_op_array breaks extension binary compatibilty (sizeof() structures have changed). so if i have an extension compiled with 4.0.2, it will core dump when run under 4.0.3p1 and vice-versa. is there an effort to maintain extension binary compatibility between minor releases, or at least a way for php to detect binary in-compatibility in extensions?

Generally, binary compatibility is not considered a primary concern at this time - doing the 'Right Thing' is. That means that changes that make sense will be made even if they break binary compatibility. In the long run maintaining binary compatibility would be a good idea, so that binary modules/extensions can be distributed. If you're talking about Zend Extensions, then they're supposed to be protected so that if the API_NO the extension was compiled with isn't the same as the one of the hosting engine, it won't load. I don't remember, it's possible that it was buggy in PHP 4.0.2. Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/