Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:5747
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 27 Nov 2003 12:12:02 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <33409013843.20031127121202@marcus-boerger.de>
To: Christian Schneider <cschneid@cschneid.com>
Cc: Andi Gutmans <andi@zend.com>, internals@lists.php.net
In-Reply-To: <3FC5D71A.3010404@cschneid.com>
References: <5.1.0.14.2.20031126172833.06829bb8@127.0.0.1>
 <5.1.0.14.2.20031126172833.06829bb8@127.0.0.1>
 <5.1.0.14.2.20031127123209.02a61918@127.0.0.1> <3FC5D71A.3010404@cschneid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Compatibility problems with PHP 5
From: helly@php.net (Marcus Boerger)

Hello Christian,

Thursday, November 27, 2003, 11:51:06 AM, you wrote:

> Andi Gutmans wrote:
>> You can use the zend2.implicit_clone INI directive (change it at 
>> run-time if you want at the beginning of the application).

> But I do want to move my application to the new semantics, I think it is 
> much more reasonable than the PHP4 behaviour anyway (sadly enough my 
> request to ref instead of copy on assignment was turned down in the PHP4 
> alpha days ;-)).

> I simply want to have a way of doing an explicit clone where it is 
> really needed. I still can't see no reason why there should be no 
> migration path for this. PHP5 adoption is going to be hard enough due to 
> subtle bugs arising from this so I think clone() is the least we could 
> do here. Forcing people to use zend2.implicit_clone won't help this IMHO.

If i get you right you want to have __clone() for PHP4, too right? But
that's already to late. And using it on PHP5 to emulate PHP4 behavior where
needed might not solve all problems, so what can we do besides __clone and
the ini directive?


-- 
Best regards,
 Marcus                            mailto:helly@php.net