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

From: Date: Mon, 27 May 2013 06:57:28 +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 12 13  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On 2013-05-27 08:49, Reinis Rozitis wrote:
Again, why can't we just bypass this whole argument by adding a configure option? Something like --date.default_timezone="America/Los_Angeles"? It could then build that in so it'll assume that if there's no php.ini or if it's just not set in there. Problem solved, everybody's use-case covered.
If you build php yourself from source there is always the option to throw (comment out) that one particular E_WARNING line ext/date/php_date.c.(that is something I do for example for mysqlnd which complains about non-existing character set on older sphinxsearch instances).
Doing that kind of modification is a straight way to introducing "custom bugs" ;) Having a community-approved setting is something different.
But if the OP is annoyed by typing "php -d date.timezone=... myfile.php" each time he could just make an alias (or doskey in win environment).
...and in all #! headers, and in all other places. That could be a temporary bypass, not a complete solution. l.

Thread (70 messages)

« previous php.internals (#67545) next »