Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64381 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25154 invoked from network); 20 Dec 2012 16:28:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Dec 2012 16:28:59 -0000 Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.28 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.28 out4-smtp.messagingengine.com Received: from [66.111.4.28] ([66.111.4.28:48636] helo=out4-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8C/27-20281-9CC33D05 for ; Thu, 20 Dec 2012 11:28:57 -0500 Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 597DD20A9E for ; Thu, 20 Dec 2012 11:28:54 -0500 (EST) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 20 Dec 2012 11:28:54 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=+dAP4rQHQWelkWqbTaM+Tx Y/8wk=; b=Nca5iSaf94gSbpIfSkSew8i1qGK3hfddPqo8Zyd8enpfTAPQWcHvV3 8UADZ7GZB2PRno9U4eeksM9mDpeT4m0DMRDo6IslBCLhyGL0l08y1bMLI9Mu507c /mzkwFN9sCxlGYklQ+4Ev9EhvIL0G95u055m0OP3sqrgCPZsZVpMM= X-Sasl-enc: gj5UZDrlI79VLIx3RZ0IxDef1W5a9+3QLyL9tKjEEQqM 1356020934 Received: from Palantirs-MacBook-Pro.local (unknown [209.41.114.202]) by mail.messagingengine.com (Postfix) with ESMTPA id 0C80C482621 for ; Thu, 20 Dec 2012 11:28:54 -0500 (EST) Message-ID: <50D33CC5.8060500@garfieldtech.com> Date: Thu, 20 Dec 2012 10:28:53 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: internals@lists.php.net References: <50C63A7C.8090705@gmail.com> <4DBD0EA5-C45B-4C12-BFE9-E263B255B2C3@strojny.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] DateTime improvement From: larry@garfieldtech.com (Larry Garfield) I've seen DateTimeValue used elsewhere for userspace immutable date time objects. Whether that indicates we SHOULD or SHOULD NOT use that for an in-C version, I don't know. (I'm inclined to say should-but-namespace, but I don't know if we're doing that yet.) Of course, I have no idea if anyone in userspace is using DateTimeImmutable... --Larry Garfield On 12/17/12 2:52 PM, Lars Strojny wrote: > Hi Derick, > > I would go with DateTimeValue or DateTimeImmutable as well. > > Am 17.12.2012 um 19:42 schrieb Benjamin Eberlei : > >> On Mon, Dec 17, 2012 at 5:48 PM, Derick Rethans wrote: >> I went for DateTimePoint. Point as in "Point in time". I am not too >> happy with the name, but I think it works better than DateTimeImmutable >> as that just sounds quircky. I'm still fixing up a few things and adding >> some test cases. I think I need to make it work with DatePeriod too - >> but I haven't looked at that yet. >> >> some suggestions: >> >> DateTimeValue >> DateTimeImmutable >> DateImmutable >> DateFixed >> DateStatic >> (and as a bonus: DateTime2) > >