Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67523 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68205 invoked from network); 25 May 2013 16:23:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 May 2013 16:23:04 -0000 Authentication-Results: pb1.pair.com header.from=nikita.ppv@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=nikita.ppv@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.53 as permitted sender) X-PHP-List-Original-Sender: nikita.ppv@gmail.com X-Host-Fingerprint: 209.85.219.53 mail-oa0-f53.google.com Received: from [209.85.219.53] ([209.85.219.53:40575] helo=mail-oa0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B2/F7-25010-865E0A15 for ; Sat, 25 May 2013 12:23:04 -0400 Received: by mail-oa0-f53.google.com with SMTP id g12so7339276oah.26 for ; Sat, 25 May 2013 09:23:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=U7mLyXP5oDx2NZ1FTEKQVOe79EJj6RZGZY9I14U88L0=; b=iIVvpeTCUrdLdNfpWl+pobdtLOQUki7VTB4bC5V8lNlg+J9mDvcFHZQZIBjAI/WRcD FZbJ3sjg2ONSJyLfmehXq0CWysf6Y3Ffj5RNbQG2Ch5jVtfmBRCr/Mitew0ITBla0Pi+ Pz7BCKk1SAKycBGj4nByemNBZjkLOBmV2/L4zA3QM95mZkgRkDmh0Sn0BtN5u6WSdPYx asZNeSJzEJIqFfC0KbtQCDe9lzPAmImP+yCq6aKe/TzfC4qwZYLIud84cbB3hTaTJcWd gZbC5EPin8TGM0vZcMehHYETXGPrL282MmVwFn3LQhaqMuoN/gratHefl2Z1P45LwyZf YI9g== MIME-Version: 1.0 X-Received: by 10.60.45.203 with SMTP id p11mr14440284oem.10.1369498981926; Sat, 25 May 2013 09:23:01 -0700 (PDT) Received: by 10.182.59.108 with HTTP; Sat, 25 May 2013 09:23:01 -0700 (PDT) In-Reply-To: References: <519E77B4.2050503@sugarcrm.com> Date: Sat, 25 May 2013 18:23:01 +0200 Message-ID: To: Daniel Lowrey Cc: Derick Rethans , Stas Malyshev , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c255f656d99a04dd8d54c8 Subject: Re: [PHP-DEV] date.timezone E_WARNING -- Really necessary? What's the rationale? From: nikita.ppv@gmail.com (Nikita Popov) --001a11c255f656d99a04dd8d54c8 Content-Type: text/plain; charset=ISO-8859-1 On Sat, May 25, 2013 at 6:04 PM, Daniel Lowrey 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 --001a11c255f656d99a04dd8d54c8--