Re: date.timezone E_WARNING -- Really necessary? What's the rationale?

From: Date: Wed, 28 Aug 2013 12:48:53 +0000
Subject: Re: date.timezone E_WARNING -- Really necessary? What's the rationale?
References: 1 2  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
I agree.


2013/8/28 Nikita Popov <[email protected]>

> On Thu, May 23, 2013 at 8:40 PM, Daniel Lowrey <[email protected]> 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 =
>
> This would mean that people running PHP without an ini would get UTC as the
> default and people running with an ini based on
> php.ini-production/php.ini-development would get the warning.
>
> Short of completely dropping the warning this is the behavior that would
> make most sense to me. (As people running without an ini obviously don't
> care about setting the timezone)
>
> Thanks,
> Nikita
>



-- 
***

Marcel Araujo
Analista de Sistemas
Desenvolvedor PHP/Zend/JavaScript/jQuery/NodeJS
Linux User #490101

http://www.twitter.com/marcelarauj0
http://blog.marcelaraujo.me
http://br.linkedin.com/in/marcelaraujo
*


Thread (70 messages)

« previous php.internals (#68636) next »