On 3 September 2012 17:36, Andrew Faulds <a...@ajf.me> wrote: > Ryan McCue <li...@rotorised.com> wrote: >>What about ISO8601 with the Olson timezone suffixed? >> >> 2012-09-02T18:17:36+0100 (Europe/London) >> 2012-09-02T18:19:05+0100 (Africa/Niamey) >> > > Sounds good.
If we're going to invent arbitrary non-standard formats, why don't we just tell people to use json_encode($dateTime) and be done with it? I just don't see how we can choose a sensible default format for users. Sometimes you want ISO 8601. Sometimes you want whatever your locale's customary date format is. Sometimes you want US m/d/y dates for interacting with legacy systems. RFC 2822. RFC 822, natch. And so on. I don't see why one format should be blessed over others and have magic behaviour when a DateTime object is cast to a string. IMO, the fact that users have to provide a format string and call format() is a good thing: explicit beats implicit, every day of the week. No matter what format string you use to iterate over said days. Adam -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
