Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65054
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.194 as permitted sender)
MIME-Version: 1.0
Reply-To: RQuadling@GMail.com
Date: Mon, 21 Jan 2013 18:36:29 +0000
Message-ID: <CAKUjMCWFftN0Xut4b6HHMHbMQL9cGw-LLSqhRQ+ofHzU8-O8Pw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: References in rfc:propertygetsetsyntax
From: rquadling@gmail.com (Richard Quadling)

Hello.

This may have already been covered, so apologies ...

With https://wiki.php.net/rfc/propertygetsetsyntax-v1.2#references,
the return by reference is handled by the use of &get{}.

How about pass-by-reference for set{}?

Normally, a function definition dictates this.

But if $value is already passed, a reference to it (&$value) is not
going to be referencing the external variable surely?

Whilst objects are always passed by reference (I assume this is still
the case for this rfc and I can see no reason why it isn't), and I
think I can see the sort of issues that setting an accessor to a
reference (binding the value of a property in this class to something
external to the class - yeah - just eek!), is this an issue?

Will users _want_ ...

set(&$value){ $this->externally_linked_var = $value; }


I'm not expecting any changes to anything, just looking for clarification.

Regards,

Richard.

-- 
Richard Quadling
Twitter : @RQuadling
EE : http://e-e.com/M_248814.html
Zend : http://bit.ly/9O8vFY