Edit report at https://bugs.php.net/bug.php?id=65352&edit=1
ID: 65352
Updated by: cataphr...@php.net
Reported by: seyferseed at mail dot ru
Summary: Method Closure::bind() can access private property
of object
-Status: Open
+Status: Not a bug
Type: Bug
Package: Class/Object related
Operating System: Linux
PHP Version: 5.4.17
Block user comment: N
Private report: N
New Comment:
Sorry, but your problem does not imply a bug in PHP itself. For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions. Due to the volume
of reports we can not explain in detail here why your report is not
a bug. The support channels will be able to provide an explanation
for you.
Thank you for your interest in PHP.
Previous Comments:
------------------------------------------------------------------------
[2013-07-31 16:42:10] mail+php at requinix dot net
References deal with the actual values of variables, not the variables
themselves. Access control deals with variables. When you create $bar as a
reference to something - anything - the only thing that matters when
changing its value is the scope of $bar.
Like a piece of paper. I write down where my buried treasure is on two
pieces, put one in a safe and give the other to you. You can use yours to
loot the treasure and replace it with your own. The fact that the other
piece of paper is locked away somewhere is irrelevant.
But here isn't the best place for an in-depth explanation of references.
Trust me when I say that what's going on isn't a bug and that plenty of
other languages act exactly the same way. If you would like a real
explanation then I suggest finding an online PHP group, forum, or mailing
list, and asking there. Or even emailing me, I wouldn't mind.
------------------------------------------------------------------------
[2013-07-31 10:49:03] seyferseed at mail dot ru
You tell me about scope, i'm understand what you mean. But in my example i can
change private property not in scrope. This is not about reading property, this
is about setting private without setter.
See examples. $bar not copy, bar link to private.
$foo = new Foo();
$bar = & $reader($foo, 'bar');
$bar = 'tab';
This is not in class scope, this is just reference (link) to private property,
but i can change it. I think this is wrong!
And in this case too:
$bar = & $foo->getBar();
$bar = "tab";
I think changing private property by reference in any case, with bind() or not,
wrong. This is violation of encapsulation.
------------------------------------------------------------------------
[2013-07-31 04:54:43] mail+php at requinix dot net
Variable scope. With bind() you were creating a closure that executes in the
scope
of that class. That's what the third argument was about. It means the function
can
do anything that a normal member function could have done, like call private
methods and access private variables.
As with reflection, with great power comes great responsibility. If you want to
get the error then omit the third argument so the function remains in the scope
you were executing in (ie, the global scope).
------------------------------------------------------------------------
[2013-07-31 04:39:12] seyferseed at mail dot ru
For PHP, yes, solved. But not for logic. I believe that to change the link to
private property is very wrong. Should generate an error.
------------------------------------------------------------------------
[2013-07-31 04:30:13] mail+php at requinix dot net
>$bar = $foo->getBar();
Simply making the function return by reference is not enough: you have to
assign
by reference too. Otherwise the function returns a reference, yes, but your
assignment makes a copy. You need both of the &s.
http://php.net/language.references.return
The first note on the page says exactly that.
Your version with Closure::bind() had both. That's why it worked.
Resolved?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=65352
--
Edit this bug report at https://bugs.php.net/bug.php?id=65352&edit=1
