Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68845
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.10.1309021047150.5679@whisky.home.derickrethans.nl>
References: <CAH8Mpnmin=caSgrOQYZD23q80eZEVO4jyRUAYKNc2URU-2RVnQ@mail.gmail.com>
	<CAF+90c_x_hooXiH52yCmGFeeW53riRhOZX7iOk2JrOJ1SFG-sA@mail.gmail.com>
	<alpine.DEB.2.10.1309021047150.5679@whisky.home.derickrethans.nl>
Date: Mon, 2 Sep 2013 13:16:54 +0200
Message-ID: <CAF+90c-mJn8Y7qf5s3yJJxkxwfrbLkSwCAJDJSG8JdN-CQsKLQ@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Daniel Lowrey <rdlowrey@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1ce68b5a48804e564b5f1
Subject: Re: [PHP-DEV] date.timezone E_WARNING -- Really necessary? What's the rationale?
From: nikita.ppv@gmail.com (Nikita Popov)

--001a11c1ce68b5a48804e564b5f1
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 2, 2013 at 11:47 AM, Derick Rethans <derick@php.net> wrote:

> On Wed, 28 Aug 2013, Nikita Popov wrote:
>
> > On Thu, May 23, 2013 at 8:40 PM, Daniel Lowrey <rdlowrey@gmail.com>
> wrote:
> >
> > > I'm probably not the typical PHP user; I spend 99% of my PHP time
> > > using the CLI (and not web SAPIs).
> > > This means that I frequently run PHP without an .ini file. As a
> > > result, when I use any of the date/time
> > > functionality I invariably end up with this awesomeness:
> > >
> > > > Warning: date(): It is not safe to rely on the system's timezone
> > > settings blah blah blah.
> > >
> >
> > I was thinking about this again and maybe we could reach the following
> > compromise:
> >
> >  * Set date.timezone = UTC as the default INI value
> >  * In php.ini-production and php.ini-development uncomment the
> >        ;date.timezone =
> >    line, i.e. change it to
> >        date.timezone =
>
> No, php.ini-development should have what PHP does by default.
>

That's not the case currently and as far as I know that is so
intentionally. ini-development and PHP defaults differ not just in obscure
extension settings, but also in core options like error_reporting,
short_tags, maximum_execution_time, variables_order, register_argc_argv,
display_startup_errors, output_buffering, etc etc etc. If these differences
are not intentional, we should fix this. But I'm pretty sure they are.

Nikita

--001a11c1ce68b5a48804e564b5f1--