It must not be a problem. Any extension that compiled for php-5.2.* must work with new php-5.2.4.
In case of objections I won't apply patch before 5.3 and in case of any claims before php-5.2.4 release I'll revert it. Dmitry. > -----Original Message----- > From: sean finney [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 03, 2007 8:04 PM > To: internals@lists.php.net > Cc: Rasmus Lerdorf > Subject: Re: [PHP-DEV] Re: [PHP-CVS] cvs: php-src > /ext/standard basic_functions.c streamsfuncs.c streamsfuncs.h > /ext/standard/tests/file include_userstream_001.phpt > include_userstream_002.phpt /main main.c php_globals.h > php_streams.h /main/streams > > > hi guys, > > On Tuesday 03 July 2007 16:48:44 Rasmus Lerdorf wrote: > > That is still a binary compatibility break. Binary compatibility > > isn't just backwards, but also forwards within a major > version. eg. > > if I build an extension against PHP 5.2.3 I expect it to > also work in > > PHP 5.2.1 and it won't in this case if the extension is > accessing this > > added element. > > hrm.. then this could potentially be a problem for 3rd party > packagers such > as debian or redhat, where there are some php extensions > which are not > generated from the main php tarball but compiled externally, > as well as any > locally compiled/installed extensions? > > sean > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
