On Sep 2, 2012 6:08 PM, "Lester Caine" <les...@lsces.co.uk> wrote: > > Peter Cowburn wrote: >> >> Finally, why should "echo $datetime;" be expected to work at all, >> since 95% of the time it's only going to be echo'd plain like that for >> debugging purposes as we'll never pick the "right" format to use in >> everyone's code. When needing to set the "default" (read: >> per-instance) string format with something like setToStringFormat() or >> whatever, that becomes*more* work than just calling format(). > > > Hopefully Will now understands just how problematic his request is, and why it has not been implemented as yet. I'm with you but for a slightly different reason. I never run anything but UTC on the server. So I'm only displaying anything other than UTC when handling a client view of the data. So I would normally be calling format with the client timezone data.
It is problematic because that is what we choose to make it. Right now, a catchable fatal error is produced. That is problematic. ISO8601 is not lossy nor is UTC. It can be taken by any other language and converted based on the format itself. We have standards for a reason. I agree that changing that should not be allowed. I will remove the set/get pattern functions and only print a standard format. Printing an ISO standard format, which includes the TZ based on UTC, or even the UTC format itself is a better solution than a catchable fatal error. > > > -- > Lester Caine - G8HFL > ----------------------------- > Contact - http://lsces.co.uk/wiki/?page=contact > L.S.Caine Electronic Services - http://lsces.co.uk > EnquirySolve - http://enquirysolve.com/ > Model Engineers Digital Workshop - http://medw.co.uk > Rainbow Digital Media - http://rainbowdigitalmedia.co.uk > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >
