Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49869 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 10150 invoked from network); 5 Oct 2010 03:48:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Oct 2010 03:48:27 -0000 Authentication-Results: pb1.pair.com header.from=ceo@l-i-e.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ceo@l-i-e.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain l-i-e.com designates 67.139.134.202 as permitted sender) X-PHP-List-Original-Sender: ceo@l-i-e.com X-Host-Fingerprint: 67.139.134.202 o2.hostbaby.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from [67.139.134.202] ([67.139.134.202:2766] helo=o2.hostbaby.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/5C-18530-A00AAAC4 for ; Mon, 04 Oct 2010 23:48:26 -0400 Received: (qmail 72170 invoked by uid 98); 5 Oct 2010 03:48:30 -0000 Received: from localhost by o2.hostbaby.com (envelope-from , uid 1013) with qmail-scanner-2.05 ( Clear:RC:1(127.0.0.1):. Processed in 0.03615 secs); 05 Oct 2010 03:48:30 -0000 Received: from localhost (HELO www.l-i-e.com) (127.0.0.1) by localhost with SMTP; 5 Oct 2010 03:48:30 -0000 Received: from webmail (SquirrelMail authenticated user ceo@l-i-e.com) by www.l-i-e.com with HTTP; Mon, 4 Oct 2010 22:48:30 -0500 Message-ID: <690cf2754d5d987eb05230bb0705f05e.squirrel@www.l-i-e.com> In-Reply-To: <4CA91151.2010104@sugarcrm.com> References: <4CA6885F.3040709@sugarcrm.com> <4CA91151.2010104@sugarcrm.com> Date: Mon, 4 Oct 2010 22:48:30 -0500 To: "Stas Malyshev" Cc: "Pierre Joye" , "Derick Rethans" , "PHP Internals" User-Agent: SquirrelMail/1.4.21 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: [PHP-DEV] rfc2616 datetime format? From: ceo@l-i-e.com ("Richard Lynch") On Sun, October 3, 2010 6:27 pm, Stas Malyshev wrote: >> It looks like a sub optimal choice to have used string constants >> instead of integer. However it could be still possible to define new >> constants as numeric. It is then possible to do whatever needs to be >> done as post or pre ops for the respective constants. > > I'm not sure what integers have to do with it? The constants define > date > formats that are in common use, RFC2616 is one of the commonest on the > web and we don't have a constant for it... I'm not sure that using 1 for RFC822, 2 for RFC884, ... would have been much better, really... You'd still have to look up the string format, and this GMT one would still be an oddball requiring pre-processing to convert to GMT, as I understand it. Perhaps a whole new "pool" of constants for gmdate() formatting??? GMT_RFC_2616, for example??? There are probably others in the same boat, yes? Let the record show that I am painfully aware of my ignorance relative to Derick with regards to Date Time matters. :-) -- brain cancer update: http://richardlynch.blogspot.com/search/label/brain%20tumor Donate: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE