Re: Re: note 69872 rejected and deleted from language.types.array by notes editor bjori

I disagree with your basic premise, which, if I may quote, goes something like this: On Mon, Sep 25, 2006 at 10:34:24PM +0100, Marcus Bointon wrote: > Requiring a reporter to know WHY a bug occurs is just obtuse > - a bug report is typically only an observation that a problem > exists, hopefully with some accuracy regarding when. If you look at the front page of bugs.php.net, one of the very first things you'll see is a list of steps we *EXPECT* every bug report to go through before it ever gets submitted to bugs.php.net. One of those steps is: Read our tips on how to report a bug that someone will want to help fix. Going through the process documented there should have, at some point, led you to one of the various mailing lists, fora, and IRC channels supporting PHP. Most of which should have at least ONE person who could have provided you with enough information to have identified this as a doc bug, rather than a code bug. It's clear to me that the person who marked the bug 'bogus' works on the code side of the project, where this clearly is a bogus bug. There simply aren't enough people who know both the code and the documentation well enough for this to have been caught at the "bug database" level, which is why we ask people to open "bug[s] that someone will want to help fix". The onus is upon the bug reporter to: A) Get the bug filed correctly; B) Get someone interested in their bug who has the power to do something about it; Unfortunate? Perhaps. But given PHP's "Open Source" roots and status, it is what it is.