On Wed, Mar 20, 2013 at 8:53 AM, Anatol Belski <a...@php.net> wrote: > Stas, > > The issue is that a warning wouldn't destroy that object. That object will > occasionally segfault PHP. E_ERROR is the simplest solution which doesn't > change the behavior of the normal operations. > > There is another one bug #53437. The patch there has E_ERROR as well, but > for the same reason. A more permissive fix would involve even more > behavior change as every method/use case of that inconsistent object > should be checked.
I think both 5.4 and 5.3 should get the original patch and not something that would not actually solves the original problem (unknown object state and possible crashes) while introducing weird error. It is not a small patch but does not change existing behaviors of the other date area, it only adds clean support for (un) serialization for this object. Cheers, -- Pierre @pierrejoye -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
