On Sat, May 25, 2013 at 6:04 PM, Daniel Lowrey <rdlow...@gmail.com> wrote:
> Granted, I don't > have to answer the bug reports, but how difficult is it to say, "No, > this is not a bug. Let me google this for you," and close as "Will not > fix?" Not difficult at all. We already have the quick-fix system in place, exactly for cases like this. It requires one, just one click in the bug mail to close the issue with an appropriate message. This is how other common bogus bugs are handled, for example people reporting "wrong float calculations". That's also why I don't buy this bug report argument. I mean, by that line of thinking we should remove the floating point quickfix and instead throw a warning on the first use of floating point numbers that asks whether the user is sure that he understands floating point arithmetic (with the ability to remove the warning with an ini setting). Sure, that's one way to avoid bogus bug requests - but it's a really, really absurd way. And in any case, if you google for things like "php time wrong", "php dates not correct" or "php time off by 5 hours" the first few results will all tell you to use date_default_timezone_set() etc. Even if you don't know about timezones, this fact should make debugging incorrect times pretty straightforward. For this the warning does not seem necessary. Nikita
