Re: Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.c zend_hash.c zend_hash.h zend_list.c zend_list.h

From: Date: Thu, 02 Aug 2001 17:40:02 +0000
Subject: Re: Re: [ZEND-ENGINE] cvs: Zend / zend.c zend_execute_API.c zend_hash.c zend_hash.h zend_list.c zend_list.h
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-61859@lists.php.net to get a copy of this message
On Thu, 2 Aug 2001, Zeev Suraski wrote: >Andi and I are in Redmond right now, so we're kinda busy with different >things... Eek! So there won't be PHP 5 but ASPv3?! (Dan said that..) :) >My personal view is that: > >- If a major (well, sub-major) version bump was required, it's really no biggy >- For this case, I don't think it's required, since the heads-up is only >for developers of PHP extensions, which are not that many. For others, it >may be a bit obscure on why the heck we bumped the version number. True. So you're saying that the people who write extensions should also be following php-dev@lists.php.net to know about any major changes? >- 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. Of course. btw. When do we get the nice, short names for the HTTP_*_VARS? --Jani >Zeev > >At 10:26 02/08/2001, Jani Taskinen wrote: > >>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 <zeev@zend.com> >> >CTO & co-founder, Zend Technologies Ltd. >> >http://www.zend.com/ >> > >> > >> > > >-- >Zeev Suraski <zeev@zend.com> >CTO & co-founder, Zend Technologies Ltd. >http://www.zend.com/ >

« previous php.dev (#61859) next »