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

On Fri, 28 Jul 2000 12:17:47 -0600, Zak Greant wrote: >At 07:40 PM 7/28/00 +0200, jalal wrote: >>Sometimes, trudging through the bug list, I come across things like >>#5833 or #5123 (thats the ereg_replace bug and the terminating script >>in comments bug). >>Are they bugs or is it just the way things work? >>Who decides? >>Or is it one of those things that should be documented and left as it >>is? >>#5833 definitely seems to be a bug to me, but then again, it is also >>wrong usage of a function. >>#5123 seems not to be a bug... but needs documenting. >> >>Any suggestions? > >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. jalal Internal docs, like commented code, are not part of the 'PHP experience'(TM).