Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62727
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain meetme.com designates 74.125.149.201 as permitted sender)
MIME-Version: 1.0
Sender: wfitch@meetme.com
In-Reply-To: <CADajX4DEtRPFP2sCeXO=xHVuGwZdPF2KW4=dQ63gzYTXsD_eVQ@mail.gmail.com>
References: <CAArmra3oN6NMn-CPn95piNQeKN1LJ7nq3baj1B0z6pCCPZX0VQ@mail.gmail.com>
	<alpine.DEB.2.02.1209021233560.25835@whisky.home.derickrethans.nl>
	<CAEZPtU7AGKYcfHBcf8ZCrAufF=MUu=75WDE28KAmhihDEFsHmw@mail.gmail.com>
	<50435ABE.4010308@ajf.me>
	<CAEPJdunLROfKuGNu3AjCjLY3KmQ4DyHJi04WkENyVg6zapVrAg@mail.gmail.com>
	<50436412.7010802@ajf.me>
	<alpine.DEB.2.02.1209021814580.25835@whisky.home.derickrethans.nl>
	<5043C3E9.2010105@ajf.me>
	<alpine.DEB.2.02.1209022145220.25835@whisky.home.derickrethans.nl>
	<5043C5AF.3060701@ajf.me>
	<alpine.DEB.2.02.1209022149540.25835@whisky.home.derickrethans.nl>
	<5043C74C.8020400@ajf.me>
	<alpine.DEB.2.02.1209022213180.25835@whisky.home.derickrethans.nl>
	<CAPg3Xx+YDJQ2buTJN9OBJ6fos+mDdxD9wdWueOZ9+d_qyuP3iA@mail.gmail.com>
	<5043D8C0.3020802@lsces.co.uk>
	<CAArmra3Oj7LfMKOf9mZpYnd6xzdhUvUPOOJLS69EbMwcc7EkNA@mail.gmail.com>
	<alpine.DEB.2.02.1209030912170.25835@whisky.home.derickrethans.nl>
	<5044715E.3050504@rotorised.com>
	<88183ff3-8037-44da-b6f9-975739600cc8@email.android.com>
	<CADajX4DEtRPFP2sCeXO=xHVuGwZdPF2KW4=dQ63gzYTXsD_eVQ@mail.gmail.com>
Date: Mon, 3 Sep 2012 07:54:49 -0400
Message-ID: <CAArmra1f-=dVYJASECpOyGYr7MN1EHewZ_8OUHPhVUVGVsczRw@mail.gmail.com>
To: Adam Harvey <aharvey@php.net>
Cc: Andrew Faulds <ajf@ajf.me>, Ryan McCue <lists@rotorised.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=bcaec502d7700b624c04c8cacf25
Subject: Re: [PHP-DEV] RFC for Adding __toString to DateTime
From: willfitch@php.net (Will Fitch)

--bcaec502d7700b624c04c8cacf25
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 3, 2012 at 5:45 AM, Adam Harvey <aharvey@php.net> wrote:

> On 3 September 2012 17:36, Andrew Faulds <ajf@ajf.me> wrote:
> > Ryan McCue <lists@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.
>

You absolutely made the case for using DateTime::format() - which is not
the proposal here.  This is for a string representation of the object via
toString.


>
> 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
>
>

--bcaec502d7700b624c04c8cacf25--