Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61041
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Amaury Bouchard <amaury@amaury.net>
Cc: internals@lists.php.net
In-Reply-To: <CAPaKmRn-1wAuicC+VRkB8+2U9fBix6iY03UmXyQOBZE+4fZPqA@mail.gmail.com>
References:
	 <CAPaKmRn-1wAuicC+VRkB8+2U9fBix6iY03UmXyQOBZE+4fZPqA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 29 Jun 2012 16:50:45 +0200
Message-ID: <1340981445.2310.5.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC proposal - Syntactic sugar for cloning
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Fri, 2012-06-29 at 16:25 +0200, Amaury Bouchard wrote:
> Back in the real world, we are not cloning objects very often. But, like
> many other syntactic sugars (as the short array syntax), I think it could
> be handy in some circumstances.

Well, arrays are used all over the place. As you said: cloning is not.
Also this patch only covers one use case, the assignment of an copy. I
does not cover other cases, like cloning in an function call
   foo(clone $obj);
etc. So I see little need for that sugar, it will mostly hurt the teeth
(to stay in the picture)

johannes