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

From: Date: Mon, 27 May 2013 07:27:21 +0000
Subject: Re: date.timezone E_WARNING -- Really necessary? What's the rationale?
References: 1 2 3 4 5 6 7 8 9 10 11  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On Mon, May 27, 2013 at 9:20 AM, Sanford Whiteman
<[email protected]> wrote:

> I am simply making the point that UTC is not the "default default"
> even when sysops or devs put their hands in. The choice isn't just UTC
> or what the end user personally sets. Domain time exists, no matter if
> Pierre has experienced it or not.

Ok, let me rephrase it in a more understandable way.

We had it the way you are wishing it. It caused hundred of side
effects, bugs reports, bad behaviors, etc. This is something we don't
want to see again. Not because either the system administrators or the
application developers are not willing to add one line to php.ini or
to their application. For all the reasoning behind this choice, please
check the numerous bugs reports and discussions on internals.

Cheers.
--
Pierre

@pierrejoye | http://www.libgd.org


Thread (70 messages)

« previous php.internals (#67548) next »