Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67545 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4323 invoked from network); 27 May 2013 06:57:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 May 2013 06:57:42 -0000 Authentication-Results: pb1.pair.com header.from=leafnode@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=leafnode@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.44 as permitted sender) X-PHP-List-Original-Sender: leafnode@gmail.com X-Host-Fingerprint: 209.85.214.44 mail-bk0-f44.google.com Received: from [209.85.214.44] ([209.85.214.44:38464] helo=mail-bk0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C4/FD-32733-6E303A15 for ; Mon, 27 May 2013 02:57:42 -0400 Received: by mail-bk0-f44.google.com with SMTP id jc3so3461746bkc.3 for ; Sun, 26 May 2013 23:57:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=0WtOq+ZM0ZXc3546reustayOg3OuqgBCYWtu+rclzA4=; b=oqXtwDAnXgSHz2Zmkd1VK4iZtJ+KylO1zqwmO+T+TNms4rcHZZsbLFyz1RD6Fsh0Rj 8uYJ+Nuwgm/HXwPkTz3APosGsOA5pYlX5wPV7EW5wKNSO3Ddiz9J5U5kcehAQksxfLyM ZWEhXEBtyNnTc7bO+rBSA7wBOIV8YqRt+Ec7KAM1TuTUzV7UjbpeLha5bsdYsjJLJJLB lW1VBU3oi1hp0+oYdmjsi6nkxLw3zRjDDDlGoZnKAIsuldcZIInndOhB22ba8efh2Kd2 H+Islr7gX0xcK9zfsQeyNeLrDp4rpsZdjAxZmAK8mzooOzbDhv90u67TcWjj+3/iIQwi 63qw== X-Received: by 10.204.237.130 with SMTP id ko2mr2435019bkb.154.1369637859410; Sun, 26 May 2013 23:57:39 -0700 (PDT) Received: from [10.0.20.40] (81-18-213-39.static.chello.pl. [81.18.213.39]) by mx.google.com with ESMTPSA id es13sm7766510bkc.8.2013.05.26.23.57.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 23:57:38 -0700 (PDT) Message-ID: <51A303D8.8030301@gmail.com> Date: Mon, 27 May 2013 08:57:28 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: internals@lists.php.net References: <51A092FC.4010700@wikimedia.org><51A1AF3E.5000704@sugarcrm.com><51A1F701.4080706@lsces.co.uk><1287105095.20130526154318@cypressintegrated.com><1445582130.20130526204520@cypressintegrated.com> <2A364FDE69FD46ECAECA939341E814DF@NeiRoze> In-Reply-To: <2A364FDE69FD46ECAECA939341E814DF@NeiRoze> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] date.timezone E_WARNING -- Really necessary? What's the rationale? From: leafnode@gmail.com (=?UTF-8?B?TGVzemVrIEtydXBpxYRza2k=?=) On 2013-05-27 08:49, Reinis Rozitis wrote: >> Again, why can't we just bypass this whole argument by adding a configure >> option? Something like --date.default_timezone="America/Los_Angeles"? It >> could then build that in so it'll assume that if there's no php.ini or if >> it's just not set in there. Problem solved, everybody's use-case covered. > If you build php yourself from source there is always the option to throw > (comment out) that one particular E_WARNING line ext/date/php_date.c.(that > is something I do for example for mysqlnd which complains about non-existing > character set on older sphinxsearch instances). Doing that kind of modification is a straight way to introducing "custom bugs" ;) Having a community-approved setting is something different. > But if the OP is annoyed by typing "php -d date.timezone=... myfile.php" > each time he could just make an alias (or doskey in win environment). ...and in all #! headers, and in all other places. That could be a temporary bypass, not a complete solution. l.