On Tue, 27 Jan 2015, Pierre Joye wrote:
> On Jan 27, 2015 11:25 AM, "Yasuo Ohgaki" <yohg...@ohgaki.net> wrote:
> >
> > On Tue, Jan 27, 2015 at 12:56 PM, Kalle Sommer Nielsen <ka...@php.net>
> > wrote:
> >
> > > I think the warning is fair as it is, if it is annoying for small
> > > use cases like on the CLI then simply: php -d date.timezone=UTC -r
> > > "echo date('H:i:s');" or the dirty way by using the silent
> > > operator. It used to be a notice prior 5.3 I think or something.
> > >
> > > While I do agree that most applications should be using UTC, which
> > > should be set by default we sometimes need to tell userland the
> > > hard way how things work, and/or what they should care about, like
> > > the E_WARNING, E_CORE_ERROR, E_DEPRECATED for old php.ini
> > > settings.
> > >
> > > -1 for removing it from my side.
> >
> > I can understand your argument. Perhaps, we may reconsider to
> > introduce E_DEBUG/E_USER_DEBUG for these purposes. There are many
> > functions, e.g. file related, that I feel E_WARNING is excessive.
>
> I do not have a strong opinion on that. So keep it or make it UTC
> default but please do not add yet another warning/notice/whatever.
>
> Also, setting a timezone is not about Dev or other fancy tasks, it is
> about making datetime processing right.
>
> If anything I would enforce the default at configure/build time. So it
> at least gets the correct one from a host point of view.
That would be nice, but it's unfortuntately not really possible. You
can't find out what timezone the OS is using in a portable way. Not even
among different linux distributions, let alone having Windows in the
mix. We tried this before, and because it caused so many issues, the
current warning was added (instead of trying to guess a timezone).
cheers,
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
