Re: A bug, or not a bug...

From: Date: Fri, 28 Jul 2000 20:34:48 +0000
Subject: Re: A bug, or not a bug...
References: 1  Groups: php.qa 
Request: Send a blank email to php-qa+get-379@lists.php.net to get a copy of this message
At 09:53 PM 7/28/00 +0200, jalal wrote: [snip]
Is the manual a definition of how the functions should work - or - are there internal docs that specify the desired behavior of a function? Both of these problems seem like simple oversights to me. Just a case that was not considered or tested for. zak Well, yes, but that doesn't really answer the question: do we document them as they are, or do we call it a bug? And who decides that? These aren't the only cases, I just hauled them up as examples.
My last posting on this was unclear. :) What I mean to say is: If there is a design document that specifies the behavior of the function, then we should use this to determine if odd behavior is a bug. I am guessing that there is no such document.... If this is the case, I feel that we should try to document what the behavior is and then give it to the developers for review. They can choose if they want to change the behavior, have it documented, whatever... Zak

« previous php.qa (#379) next »