[PHP-DEV] extension 4.0.6 -> 4.2.2

Hi, I'm began converting a module I wrote for 4.0.6, and I use this code: if ((zend_hash_find(&EG(symbol_table), "HTTP_SERVER_VARS", sizeof("HTTP_SERVER_VARS"), (void **) &data) != FAILURE) && Z_TYPE_PP(data) == IS_ARRAY) In 4.2.x, I just change this to _SERVER, or is there another "fancier"

Re: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1?

Aren't most of your problems related to using a 64-bit platform? Where were you during QA on 4.2? My sort() stuff works just fine here. -Rasmus On Sun, 28 Jul 2002, Sebastian Nohn wrote: > Hi, > > > there are not enough people for this. > > Well. As I already said: Then there are'nt enough pe

[PHP-DEV] CVS Account Request: vmarshall

Work on presentation system. -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi, > The other major problem is availibilty of platforms QA'd. Sebastian - I > trust you'll take the two 64-bit systems you we're talking about? Uh. Yes well... The next week this is no problem, after that I have vacation and I only have access to these machines from my office so I would one ch

Re: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

At 20:44 28-7-2002, [EMAIL PROTECTED] wrote: > > Well. As I already said: Then there are'nt enough people for 4.3.0 too. Yes > > I know, you are the maintainer of 4.2.x, Stig is the maintainer of 4.3.0. > >There are not enough people to do two releases at one time. Actually - one issue there, ar

[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

> Following that, why not do what a number of people do, and do > > major.minor.patch > > major releases say every 6 months > minor ones every 2 - unless serious patch required > patches as required > > This allows people to predict the times also. > i would see this working, given it's what we do

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi, > > That is no solution for the real problem. People are frustrated > > because they don't know if their software runs on the next machine > > they put it on because this machine maybe has another PHP-version. > > It's the same thing like GD or Apache 2. Why was GD forked by PHP, > > why was

Re: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1?

On Sun, 28 Jul 2002, Sebastian Nohn wrote: > Hi, > > > there are not enough people for this. > > Well. As I already said: Then there are'nt enough people for 4.3.0 too. Yes > I know, you are the maintainer of 4.2.x, Stig is the maintainer of 4.3.0. There are not enough people to do two release

[PHP-DEV] Re: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

On Sun, 28 Jul 2002, Sebastian Nohn wrote: > That is no solution for the real problem. People are frustrated because they > don't know if their software runs on the next machine they put it on because > this machine maybe has another PHP-version. It's the same thing like GD or > Apache 2. Why was

RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi, > > Yes. That may be. But there are a lot of bugfixes in the latest > > STABLE-snapshot I tested (26/07/02) - or exactly: All bugs I experienced > > were fixed. So the easiest thing would be to cancel all new > > features that were planned for 4.2.3 and move them to 4.3.0 and apply all > > pa

[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi, > there are not enough people for this. Well. As I already said: Then there are'nt enough people for 4.3.0 too. Yes I know, you are the maintainer of 4.2.x, Stig is the maintainer of 4.3.0. Regards, Sebastian Nohn -- +49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/ PGP Key Ava

RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

On Sun, 28 Jul 2002, Sebastian Nohn wrote: > Yes. That may be. But there are a lot of bugfixes in the latest > STABLE-snapshot I tested (26/07/02) - or exactly: All bugs I experienced > were fixed. So the easiest thing would be to cancel all new features that > were planned for 4.2.3 and move the

Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Easy answer: there are not enough people for this. Derick On Sun, 28 Jul 2002, Liz wrote: > Another option would be to get people to split into 2 teams, and have > bug fix team and new feature team, where people specifically look at > those features. Make a slightly bigger divide between the t

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

On Sun, 28 Jul 2002, Sebastian Nohn wrote: > Hi, > > > has at least as few bugs as 4.0.4pl1. At least a 4.0.2pl1 fixing > > the so far > > That is 4.2.2pl1 of course ;) The next version should be 4.2.3, and not pl1 crap :) Derick -

[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

At 19:40 28-7-2002, Liz wrote: >Following that, why not do what a number of people do, and do > >major.minor.patch Basically that's how it is, but the understanding of major and minor is a little outof sync with other packages out there or QA of minors isn't wat is should be, which ever you pre

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi, > we released 4.2.2 less than a week ago. If we release any new > package within 2weeks to a month, i feel it'll just infuriate system admins more. > People don't want to be installing new packages every week for the same product. We were running 4.0.4pl1 for more than one year, then we need

[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Following that, why not do what a number of people do, and do major.minor.patch major releases say every 6 months minor ones every 2 - unless serious patch required patches as required This allows people to predict the times also. -- PHP Development Mailing List To uns

[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

the large amount of time between the branches. > > Yes. That may be. But there are a lot of bugfixes in the latest > STABLE-snapshot I tested (26/07/02) - or exactly: All bugs I experienced > were fixed. So the easiest thing would be to cancel all new features that > were planned for 4.2.3 and mo

RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi, > Because we have no 4.2 release manager with Derick going away. And 4.3 > fixes a whole slew of 4.2 bugs And brings 150 new... > some of which are not easily backportable to the 4.2 codebase because of > the large amount of time between the branches. Yes. That may be. But there are a lot

Re: [PHP-DEV] Patch to add profiling support to PHP at the PHP level

The nice thing about a module which dumps external files is taht you can use the raw data in any number of ways. For example with APD, you can generate a complete call graph, provide statics inclusive or exclusive of child calls, and do rather arbitrary type sorting. This is seems to be the

Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Because we have no 4.2 release manager with Derick going away. And 4.3 fixes a whole slew of 4.2 bugs some of which are not easily backportable to the 4.2 codebase because of the large amount of time between the branches. -Rasmus On Sun, 28 Jul 2002, Sebastian Nohn wrote: > Hi, > > > Another o

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hey Liz, At 15:55 28-7-2002 +0100, Liz wrote: >Another option would be to get people to split into 2 teams, and have >bug fix team and new feature team, where people specifically look at >those features. Make a slightly bigger divide between the two projects. Yes - for QA this is a good idea. C

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi, > Another option would be to get people to split into 2 teams, and have > bug fix team and new feature team, where people specifically look at > those features. Make a slightly bigger divide between the two projects. Why not simple delay another buggy release 4.3.0? Regards, Sebastian No

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Another option would be to get people to split into 2 teams, and have bug fix team and new feature team, where people specifically look at those features. Make a slightly bigger divide between the two projects. > Yes, there are others who feel this way - but basically it > boils down to > who is

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi Sebastian, At 16:08 28-7-2002 +0200, Sebastian Nohn wrote: > > yes it was, but it was canceled, as Stig, Derick and others > > agreed, that it would delay 4.3.0 too much. > >Nobody needs 4.3 with 1000 new features, everybody needs a PHP Version that >has at least as few bugs as 4.0.4pl1. At l

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi, > has at least as few bugs as 4.0.4pl1. At least a 4.0.2pl1 fixing > the so far That is 4.2.2pl1 of course ;) Regards, Sebastian Nohn -- +49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/ PGP Key Available - Did I help you? Consider a gift: http://www.amazon.de/exec/obidos/wis

[PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

Hi, > yes it was, but it was canceled, as Stig, Derick and others > agreed, that it would delay 4.3.0 too much. Nobody needs 4.3 with 1000 new features, everybody needs a PHP Version that has at least as few bugs as 4.0.4pl1. At least a 4.0.2pl1 fixing the so far closed bugs would be great. I ha

[PHP-DEV] CVS Account Request: 52

i love php -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] vacation

Hello, I'm taking a vacation in which I won't be answering any email. I'll get back to you as soon as I get back on August 17th. Derick --- Derick Rethans http://www.derickrethans.nl/ JDI M

[PHP-DEV] Patch to add profiling support to PHP at the PHP level

Hello, I made a patch to add PHP profiling support to the PHP language. It adds 'set_profile_handler' and 'restore_profile_handler' that work similar to the 'set_error_handler' and 'restore_error_handler' functions and are the minimum needed to allow people to profile their PHP code directly from

[PHP-DEV] Re: #18417 [Opn->Bgs]: pg_fetch_array says Unable to jump to row0 on PostgreSQL result index

Melvyn Sopacua wrote: > Is there any chance you can make the second argument optional? > This makes it easier to write db classes, which are interchangeable > between mysql and pgsql. It's already a optional, you can ommit 2nd parameter, if you want. I think I've changed doc also. If not, let me

[PHP-DEV] Re: #18417 [Opn->Bgs]: pg_fetch_array says Unable to jump to row 0 on PostgreSQL result index

Yasuo, this actually raises a point I've been meening to ask you about. Is there any chance you can make the second argument optional? This makes it easier to write db classes, which are interchangeable between mysql and pgsql. I think It currently can be done in php, but you'd need to make an