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 <kont...@beberlei.de>:
On Mon, Dec 17, 2012 at 5:48 PM, Derick Rethans <der...@php.net> 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)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
