Re: [PHP-DEV] Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.czend_hash.c zend_hash.h zend_list.c zend_list.h
On Thu, 02 Aug 2001, Zeev Suraski wrote: zeevThu Aug 2 09:16:20 2001 EDT Modified files: /Zend zend.c zend_execute_API.c zend_hash.c zend_hash.h zend_list.c zend_list.h Log: Some cleanup I really wish all these TSRM changes were left for 4.1. There are just way too many functions affected and I guarantee you that all the standalone extensions will be broken because people will not expect such breakage from a point release. It also breaks binary compatibility forcing everyone to release new extensions. The change from ZEND_API void wrong_param_count() to ZEND_API void zend_wrong_param_count(TSRMLS_D) Makes extensions built for 4.0.6 break against current CVS right now: PHP Warning: Unable to load dynamic library '/usr/local/lib/php/php_ming.so' - /usr/local/lib/php/php_ming.so: undefined symbol: wrong_param_count in Unknown on line 0 -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.czend_hash.c zend_hash.h zend_list.c zend_list.h
Andrei Zmievski wrote: I really wish all these TSRM changes were left for 4.1. Why not skip 4.0.7 and make 4.0.7-dev PHP 4.1.0? -- Sebastian Bergmann Measure Traffic Usability http://sebastian-bergmann.de/http://phpOpenTracker.de/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.czend_hash.c zend_hash.h zend_list.c zend_list.h
[I'm just catching up] I'd like the PHP streams stuff to get into 4.1, but I am lacking time for a few weeks. If we were to go for 4.1, are there any plans for when? --Wez. On 02/08/01, Rasmus Lerdorf [EMAIL PROTECTED] wrote: Zeev Suraski wrote: - For the register_globals default change, I believe a major version bump is a very good idea, as it's exactly the kind of heads-up message we want to send to all of the users. Why not combine the two for a 4.1 release? How much work would be required to do the register_globals default change now? I would pretty much insist on the _GET() stuff, import_globals() and register_globals changes being implemented in 4.1. With these TSRM changes, the register_globals changes and hopefully Sterling's XSLT changes I think there is enough new stuff and incompatible changes to warrant a 4.1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.czend_hash.c zend_hash.h zend_list.c zend_list.h
It's time to break the evil spell on the middle number. IMO, it does really matter if it is 4.1.0 or 4.0.7.. It's the HEADS UP! for people when you change the more significant version number. (and also gives a nice backdoor for breaking bc without wtf-factor :) If someone is afraid of changing it, I can volunteer. ;) Another thing, I get a segfault when php is configured like this: ./configure --with-crack=/usr/src/cracklib.2.7 --enable-experimental-zts --Jani p.s. Zeev, you're only idling on IRC nowadays? On Thu, 2 Aug 2001, Zeev Suraski wrote: It should be fairly easy to support both codebases by just defining the right things depending on the API_NO. At any rate, whether we call it 4.1 or 4.0.7 doesn't really matter. It had to be done, and would involve the same kind of issues regardless of the name. Zeev At 06:47 02/08/2001, Andrei Zmievski wrote: On Thu, 02 Aug 2001, Andrei Zmievski wrote: I really wish all these TSRM changes were left for 4.1. There are just way too many functions affected and I guarantee you that all the standalone extensions will be broken because people will not expect such breakage from a point release. Oh, as an example PHP-GTK v0.1 now has to require latest PHP CVS or 4.0.7 because of this. Not too good. -Andrei The only true currency in this bankrupt world is what we share with each other when we're uncool. -- Lester Bangs, from the film 'Almost Famous' -- Zeev Suraski [EMAIL PROTECTED] CTO co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.czend_hash.c zend_hash.h zend_list.c zend_list.h
The register_globals change must go through one iteration where we have the new APIs available, but still haven't changed the default. So, we can't combine these two changes together... Zeev At 10:41 02/08/2001, Sebastian Bergmann wrote: Zeev Suraski wrote: - For the register_globals default change, I believe a major version bump is a very good idea, as it's exactly the kind of heads-up message we want to send to all of the users. Why not combine the two for a 4.1 release? How much work would be required to do the register_globals default change now? -- Sebastian Bergmann Measure Traffic Usability http://sebastian-bergmann.de/http://phpOpenTracker.de/ -- Zeev Suraski [EMAIL PROTECTED] CTO co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.czend_hash.c zend_hash.h zend_list.c zend_list.h
On Thu, Aug 02, 2001 at 10:50:07AM -0700, Rasmus Lerdorf wrote: I would pretty much insist on the _GET() stuff, import_globals() and register_globals changes being implemented in 4.1. With these TSRM changes, the register_globals changes and hopefully Sterling's XSLT changes I think there is enough new stuff and incompatible changes to warrant a 4.1 In that case, release 4.1 will be considered both an continuation of the 4.0.x line as well as a new standard for development. That presupposes there will be no 4.0.x maintenance branch or future 4.0.x releases. I'm not objecting. I just think it's worth pointing out the ramifications of releasing 4.1 now (well, soon) with these changes. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
