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

Hello, Am Montag, 27. Mai 2013 um 09:27 schrieb Pierre Joye: > On Mon, May 27, 2013 at 9:20 AM, Sanford Whiteman > <swhitemanlistens-software@cypressintegrated.com > (mailto:swhitemanlistens-software@cypressintegrated.com)> 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. > would it be hard to just show the notice as soon as the user actually uses a function regarding to date/time (and not before)? Currently the message is shown all the time, at the start of the script - even if the script is as simple as <?php echo 1; Wouldn't it be more useful if the notice only appears, if I actually use a date/time-function? -- Cheers Jannik > > Cheers. > -- > Pierre > > @pierrejoye | http://www.libgd.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >