Hello, Markus Fischer wrote: > > On Sat, Dec 15, 2001 at 11:43:07PM -0200, Manuel Lemos wrote : > > Sure but they way it seems to me is that reporting the problem did not > > make any difference. So why bother reporting? > > Just because yours was rejected doesn't mean all were or will > be rejected. Globalising something from a subjective > expirience isn't a very good idea ;)
Gee, Markus, have you just arrived to php-dev? :-) PHP developers have a very long track record of neglecting my bug reports and quality improvement suggestions, some times making a very hard effort to deny that what I am reporting it is a bug! I could tell you about at least of handful of never address cases, but I just leave to do a search in the bug database for bug reports submitted by [EMAIL PROTECTED] . > > I am afraid that a lot of people simply do not bother to report > > problems, even when it affects their businesses, because they just get > > this kind of response and they certainly can use the time they spend > > making a useful report in things that can really result in something > > that the need. > > .. and many people are actually reporting bugs (as we > obviously can see :). You'll just have to realize that the > dev team can't please everybody. My point is that many of those people will give up reporting after they realize than many of their reports are simply not being properly addressed! > That the particular problem missbehaved in the past for so > long is a pitty. That it's not documented is a pitty. > Changing this behaviour BACK AGAIN is IMHO the worst thing > one can think of. What I suggested was not to change to the original behaviour, but rather have a switch in php.ini to enable the original behaviour. > IMHO the best thing we can and should do at the moment is to > proper document this change down and from that point of view > your report was very valueable. Never mind, functions like dirname and strtok are in my blacklist, meaning I will ban them from my PHP programs because I can't afford using or distribute code that does not provide reliable behaviour as I can't assure if my code will run with a PHP version that will provide a reliable behaviour. strtok for instance had a long track record of bugs. Not a very long time ago, I banned strtok from Metabase because a user complained that Metabase could not be used in PHP session handlers. It turned out that it was a bug in strtok. As you know many thousands of use Metabase, so I can't be responsible for strtok bugs that affect Metabase. I completely removed all calls to strtok in Metabase. The same story with dirname. I just realized that strtok has a new bug caused by somebody that tried to fix a previous report. Now it affects the whole PHP Classes site. So, now I will ban strtok from all my PHP software. I used to say as a joke that I don't use Microsoft software because it is already hard to keep my software bug free so it would be harder if it dependended on Microsoft software. Too bad that is not a joke with PHP. :-( This is just my view of what it means to be professional when you develop software that many others use. Too bad that not everybody agrees. :-( Regards, Manuel Lemos -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
