Re: __clone() implementation
| From: | Andi Gutmans | Date: | Mon, 02 Feb 2004 19:39:29 +0000 |
| Subject: | Re: __clone() implementation | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-7485@lists.php.net to get a copy of this message | ||
At 07:32 PM 2/2/2004 +0100, Ferdinand Beyer wrote:
On 2 Feb 2004 at 14:36, Zeev Suraski wrote: Clone methods must now be declared as follows: function __clone($that) { } I just had a look at zend_compile.c - it seems as if the variable name $that was mandantory: [...] || strcmp(CG(active_op_array)->arg_info[0].name, "that")!=0)) {Because we want to keep it standard so that everyone uses the same thing (like previously). Anyway, $clone is semantically wrong because it implies that is the cloned object and not the to-be-cloned object. Andizend_error(E_COMPILE_ERROR, "The clone methodmust be declared as __clone($that)"); [...] Why shouldn't I be able to name it as I want, e.g. $clone? Don't understand the reason for that...