Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62696
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain meetme.com designates 74.125.149.149 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5043D8C0.3020802@lsces.co.uk>
References: <CAArmra3oN6NMn-CPn95piNQeKN1LJ7nq3baj1B0z6pCCPZX0VQ@mail.gmail.com>
	<5042BC3C.7070208@sugarcrm.com>
	<CAArmra16sTbcYmORDK2mesFOeZxsD=3rAH03S3B_MRJnE8J6Gw@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>
Date: Sun, 2 Sep 2012 19:04:12 -0400
Message-ID: <CAArmra3Oj7LfMKOf9mZpYnd6xzdhUvUPOOJLS69EbMwcc7EkNA@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b5da23d19242604c8c00bad
Subject: Re: [PHP-DEV] RFC for Adding __toString to DateTime
From: wfitch@meetme.com (Will Fitch)

--047d7b5da23d19242604c8c00bad
Content-Type: text/plain; charset=ISO-8859-1

On Sep 2, 2012 6:08 PM, "Lester Caine" <lester@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
>

--047d7b5da23d19242604c8c00bad--