Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81505
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54CD6AD6.9080209@gmail.com>
References: <CALW=WECRvkHOJXre3s26K0zGic4d1m5pVQVOKT0=ssO9heyyAw@mail.gmail.com>
	<54CD6AD6.9080209@gmail.com>
Date: Sun, 1 Feb 2015 02:15:18 +0200
Message-ID: <CALW=WEDFmUXap7Bx=chHx5VYHcOi1kBahgDkJiF2aDLx6YT6Jg@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Use "caller" keyword, to access object caller.
From: ua.san.alex@gmail.com ("S.A.N")

2015-02-01 1:52 GMT+02:00 Stanislav Malyshev <smalyshev@gmail.com>:
> Hi!
>
>> The reason for creating circular references, usually due to the need to
>> bind objects.
>>
>> But this relationship can often be obtained from the context of the call.
>
> If the API behaves differently depending on who is calling it, or
> requires some information from the caller, it should be passed
> explicitly - as a parameter/method call/etc. - not hidden. Otherwise it
> would lead to nasty surprises when the user of the API assumes caller
> does not matter but the implementor assumes it does.
> --
> Stas Malyshev
> smalyshev@gmail.com

This is a controversial statement.
If  the caller explicitly send the object as an argument, it worsens
loose depending API.

And agreed this code looks weird and not well thought-out:
<?php

$holder->object->call($holder);

?>

Opportunity to shoot yourself in the foot, will always, developers
node.js it know.

I know that this code can be arranged differently, but then you have
to make it more difficult and not nice.

But if have an easy way to get a pointer to the owner, in practice, is
very convenient.