Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62699 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56977 invoked from network); 2 Sep 2012 23:12:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Sep 2012 23:12:30 -0000 Authentication-Results: pb1.pair.com header.from=theanomaly.is@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=theanomaly.is@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender) X-PHP-List-Original-Sender: theanomaly.is@gmail.com X-Host-Fingerprint: 209.85.215.42 mail-lpp01m010-f42.google.com Received: from [209.85.215.42] ([209.85.215.42:43490] helo=mail-lpp01m010-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 99/8C-17065-CD7E3405 for ; Sun, 02 Sep 2012 19:12:28 -0400 Received: by lahl5 with SMTP id l5so3293637lah.29 for ; Sun, 02 Sep 2012 16:12:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=G0AHQjKyEVWJemv+nRBF0b49n7t5/9oYZAlpTbil6gM=; b=HEUQ5EZ+Yf8F+6SqLNMlyOSAJwp7YFjzxjtqnGOzHqv7IVk98pcYXmQWTx2Gwwm2+3 xXq990krOFbmSUiy39rrgmwKzKjt9/H7EFK+HFC8YuRSdyi+qGLhRkUtMbSWkgVjhsmU 5OFyuQRPWnalpVR1sHKbbD9i11AK8K0f2qdQ+ZBzxcMcjuP0X2Q7Rrul7hnuvs+nSS50 aGl1a1qYY0yEHuzYiZh5eE26AwBM0mahhx0dfK7LQjlIoTkOwT043uf3Fyk29UwlJLDi 9bn+Sh4VL2r4Le5dZ6Zpqw/fpGUkATZFKpAEAgM0ZY6gaGmTiJjiIwf7a+NBTALdB0Le p+fw== MIME-Version: 1.0 Received: by 10.112.86.102 with SMTP id o6mr4595497lbz.113.1346627545668; Sun, 02 Sep 2012 16:12:25 -0700 (PDT) Received: by 10.112.12.178 with HTTP; Sun, 2 Sep 2012 16:12:25 -0700 (PDT) In-Reply-To: References: <5042BC3C.7070208@sugarcrm.com> <50435ABE.4010308@ajf.me> <50436412.7010802@ajf.me> <5043C3E9.2010105@ajf.me> <5043C5AF.3060701@ajf.me> <5043C74C.8020400@ajf.me> <5043D8C0.3020802@lsces.co.uk> Date: Sun, 2 Sep 2012 19:12:25 -0400 Message-ID: To: "internals@lists.php.net" Cc: Will Fitch Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] RFC for Adding __toString to DateTime From: theanomaly.is@gmail.com (Sherif Ramadan) On Sun, Sep 2, 2012 at 7:11 PM, Sherif Ramadan wrote: >> >> 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. >> I don't understand why that's problematic? The user wants to output a formated date they should provide a format by calling DateTime::format()... why do we have to assume the user will find *any* standards we propose to be acceptable? As you can see everyone here that uses it expects something slightly different. This request makes no sense. Sorry. >> 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 >>>