Re: rfc2616 datetime format?
| From: | Derick Rethans | Date: | Mon, 04 Oct 2010 08:42:15 +0000 |
| Subject: | Re: rfc2616 datetime format? | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-49860@lists.php.net to get a copy of this message | ||
On Mon, 4 Oct 2010, Pierre Joye wrote:
> On Mon, Oct 4, 2010 at 1:27 AM, Stas Malyshev <smalyshev@sugarcrm.com> 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 mean in ext/date and as a reply to Derick, not your request which is
> totally valid. A date time object has the timezone information. If the
> constants were integers, it would be very straightforward to do some
> operations before calling the formatting functions depending on a
> given predefined format. It should still be possible to do it by
> testing the string contents (strncmp), but that's not very clean.
Stop talking about something you don't know anything about, please.
Those constants are not *one* format letter, they are many. Maybe you
could have tried this:
echo DateTime::RFC822, "\n";
Derick