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).
I don't see why you should remove the clone functionality of these extensions if they work with standard PHP 5? The fact that it doesn't work with compatibility mode isn't a good enough reason in my opinion. That said, what you could do is have two sets of handlers arrays, one with the clone and one with NULL. You can then check ze1.compatibilit_mode in the extension and use the relevant handlers array.
What do you think?
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
