That would be fine to not allow the problem extensions to run under ze1 and end up issuing zend_error(E_ERROR, "Trying to clone an uncloneable object of class %s", Z_OBJCE_P(value)->name) (which currently happens when no clone handler is implimented).
In order for that to happen though the extensions cannot support the new clone syntax either since they use the same handler. If there arent going to be any changes to the way this works, then I would like to make a BC break in these extensions right now while its still early and remove their clone functionailty (so far it would be dom, xsl and simplexml as I have only been testing this with the xml extensions). Rob From: Andi Gutmans > I understand the problem although I haven't analyzed it in as much depth as > you have as to when exactly it happens. > The thing is that I see compatibility_mode as something which is supposed > to help make most old scripts run with PHP 5. I think scripts that take > advantage of new PHP 5 features such as SimpleXML and friends should be > required to not run in compatibility_mode. > No I know DOM existed in PHP 4, but it has changed and I think it's fair to > require that if a person ports their application to PHP 5 DOM then they > port the whole thing. > You know I'm probably one of the strongest BC advocated on this list but I > think it's best not to change this. > Do you understand where I'm coming from? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
