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

On Sun, May 26, 2013 at 11:49 PM, Reinis Rozitis <r@roze.lv> 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). > > > 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). > > > rr > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Well yes, but you could make the same argument for a lot of the configure options that are already in place. Personally, if such a configure option existed, I'd probably use it myself, since date.timezone is generally the only manual modification I have to make to php.ini, anyway. If I could set that in configure, I wouldn't have to bother with php.ini at all when doing installs. If there's no downside to adding that option (at least I haven't seen anybody offer one yet) and it has a reasonable use-case (which it does), then why not? It would certainly make a lot more sense than manually editing the source code, particularly for sysadmins who might not have any programming experience. --Kris