On Sun, Dec 5, 2010 at 7:02 PM, troels knak-nielsen <troel...@gmail.com> wrote: > On Sun, Dec 5, 2010 at 6:44 PM, Benjamin Eberlei <kont...@beberlei.de> wrote: >> So currently preferred over my patch are two solutions: >> >> 1. Just create a DateTimeValue object that is immutable, not optimizing PHP >> to handle it with efficient garbage collection. >> 2. One step further, add a "static class DateTimeValue" like syntax that >> creates an immutable class. >> >> Any ideas? > > I'd prefer BC breakage. DateTimeValue just doesn't have a good ring to > it. Besides, having two both a mutable and an immutable version at the > same time is bound to cause confusion.
It is not only about date but about create value type. There are plenty of good usages for such thing. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
