Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21751
Return-Path: <derick@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 61736 invoked by uid 1010); 1 Feb 2006 08:34:55 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 61721 invoked from network); 1 Feb 2006 08:34:55 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 1 Feb 2006 08:34:55 -0000
X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4)
Received: from ([82.94.239.5:33060] helo=jdi.jdi-ict.nl)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id A4/6D-23224-EA270E34 for <internals@lists.php.net>; Wed, 01 Feb 2006 03:34:54 -0500
Received: from localhost (localhost [127.0.0.1])
	by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id k118YnKR012106;
	Wed, 1 Feb 2006 09:34:49 +0100
Received: from localhost (localhost [127.0.0.1])
	by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id k118Ykhf012087;
	Wed, 1 Feb 2006 09:34:46 +0100
Date: Wed, 1 Feb 2006 09:34:45 +0100 (CET)
X-X-Sender: derick@localhost
To: Hannes Magnusson <hannes.magnusson@gmail.com>
cc: internals@lists.php.net
In-Reply-To: <7f3ed2c30601311337i4028d9e3ye12f1916f442edd9@mail.gmail.com>
Message-ID: <Pine.LNX.4.62.0602010933500.5039@localhost>
References: <7f3ed2c30601311337i4028d9e3ye12f1916f442edd9@mail.gmail.com>
X-Face: "L'&?Ah3MYF@FB4hU'XhNhLB]222(Lbr2Y@F:GE[OO;"F5p>qtFBl|yVVA&D{A(g3[C}mG:199P+5C'v.M/u@Z\![0b:Mv.[l6[uWl'
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new at jdi-ict.nl
Subject: Re: DATE_ISO8601 and the "c" date() character
From: derick@php.net (Derick Rethans)

On Tue, 31 Jan 2006, Hannes Magnusson wrote:

> I just noticed that the DATE_ISO8601 constant and the "c" date()
> character don't give the same results.
> The difference is that the "c" format prints colon in the timezone
> offset, but the constant does not - both are however ISO8601
> compliant.

<snip>

> However! I think ISO8601 formats without the colon are more used..,
> not sure if this should be changed at all....

Indeed, I don't think we should change this. As long as it is properly 
documented of course.

regards,
Derick
-- 
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org