Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81397
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CALW=WECRvkHOJXre3s26K0zGic4d1m5pVQVOKT0=ssO9heyyAw@mail.gmail.com>
References: <CALW=WECRvkHOJXre3s26K0zGic4d1m5pVQVOKT0=ssO9heyyAw@mail.gmail.com>
Date: Thu, 29 Jan 2015 22:50:53 -0500
Message-ID: <CA+sv8zAz1Vy5hmDSVMoPAAz-G9SRACLfhu5r+O7Y0-OZswJjbw@mail.gmail.com>
To: "S.A.N" <ua.san.alex@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec51824a8dbbd71050dd68291
Subject: Re: [PHP-DEV] Use "caller" keyword, to access object caller.
From: jrbasso@gmail.com (Juan Basso)

--bcaec51824a8dbbd71050dd68291
Content-Type: text/plain; charset=UTF-8

Usually it is solved sending the $this instance to class C constructor and
C object storing it in some attribute, solving the problem. I don't think a
new keyword would help.

Juan Basso

On Thu, Jan 29, 2015 at 9:53 PM, S.A.N <ua.san.alex@gmail.com> wrote:

> 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.
>
> It will be very convenient to have a keyword that will return reference to
> an object, which caused this object.
>
> Sorry for my English, I'm not a native speaker.
> A simple example below shows the behavior that we need.
>
> <?php
>
> class A
> {
>     public function __construct() {
>         $this->object = new C;
>     }
> }
>
> class B
> {
>     public function __construct() {
>         $this->object = new C;
>     }
> }
>
> class C
> {
>     public function getCaller() {
>         return caller::class;
>     }
> }
>
> $a = new A;
> $b = new B;
> $c = new C;
>
> $a->object->getCaller(); // return A
> $b->object->getCaller(); // return B
>
> $c->getCaller(); // Fatal Error - undefined caller context
>
> ?>
>
> Create a new keyword can cause problems with backward compatibility...
> Perhaps you can solve a problem to using an existing keyword?
>
> Thank you for any feedback.
>

--bcaec51824a8dbbd71050dd68291--