Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:11576 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20776 invoked by uid 1010); 26 Jul 2004 14:26:50 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 20746 invoked from network); 26 Jul 2004 14:26:50 -0000 Received: from unknown (HELO ctindustries.net) (216.117.147.250) by pb1.pair.com with SMTP; 26 Jul 2004 14:26:50 -0000 Received: from ctdprimary (dsta-aa203.pivot.net [66.186.171.203]) (authenticated bits=0) by ctindustries.net (8.12.8/8.12.8) with ESMTP id i6QDPUbx006639 for ; Mon, 26 Jul 2004 09:25:35 -0400 Message-ID: <019501c4731d$043451c0$f7dea8c0@cyberware.local> To: Date: Mon, 26 Jul 2004 10:29:49 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Subject: explicit clone vs implicit zend.ze1_compatibility_mode clone From: rrichards@ctindustries.net ("Rob Richards") Referencing bug 29386, I am not sure wether this would be considered a bug or expected behavior. It looks like in order to support using an explicit clone call, you also have to support implicitly called clones when zend.ze1_compatibility_mode clone is set on. It seems to be an all or nothing there. If this would not considered expected behavior, then is there some way to define 2 different clone handlers so that ze1 compatibility would use a different handler? - I couldnt find a way while looking through the code. The problem arises, in this case, that an explicit clone call works correctly as the internal object needs to be cloned, but when it is called implicitly, the internal object shouldnt be cloned. Really would just like to create a new object (zval - which would be pointing to the current internal object). This behavior isnt limited to dom, as the same behavior can be reproduced using simpleXML due the interdependancy of the libxml nodes and implicit cloning breaking the hierarchy. Not sure if this issue exists elsewhere. Rob