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

From: Date: Fri, 24 May 2013 08:16:33 +0000
Subject: Re: date.timezone E_WARNING -- Really necessary? What's the rationale?
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On Fri, May 24, 2013 at 12:11 AM, Levi Morrison <[email protected]>wrote:

> >>> The "U" in UTC *does* stand for "Universal," after all.
> >>> It's a
> >>> sensible default and as such shouldn't
> >>
> >> I don't think it's a sensible default - people don't actually use UTC
> >> when considering dates. A minority of people can use timezone that
> >> coincides with UTC, but not very many use actual UTC.
> >
> > I was wondering - why not get time zone info from operating system? It's
> > should be quite easy on both *nixes and Windows. That way default value
> > would be "from operating system", with possibility to override it in
> .ini.
>
> I believe this may have been the behavior at some point; at least
> date_default_timezone_get change in PHP 5.4 to no longer includes info
> from the OS.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Couldn't we take a page from MySQL's book and have a setup script that
prompts the admin for this (much like theirs prompts for a root password).
 A reminder to run it could be added as a nag at the end of the install;
or, perhaps even have it give you these setup prompts at the end of make
install.  This way, any environment-specific settings we think should be
there that don't have obvious defaults, like date.timezone, could be added
as prompts in the setup script.  This would enable even inexperienced
admins to add these settings without cluttering-up the bugs tracker.

Thoughts?

--Kris


Thread (70 messages)

« previous php.internals (#67482) next »