Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91520
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.46 as permitted sender)
References: <CAF8MkRhYJZApgQbr16DmDdFxET9ORkah9jxabL7nbHFKYh0N1A@mail.gmail.com>
 <94.96.08749.188B8D65@pb1.pair.com>
 <CANaX5nfHALhKJcf2B46sz0hc5gDu+dY7J_kD17SM=MXH4hLvqg@mail.gmail.com>
 <56D95E18.9020007@gmail.com>
 <CANaX5ne6s+q8tBRgt0WetC5z8R7C5Rc5-cqXB7frXQiSZ4WO9A@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Message-ID: <56DC6C32.4070801@gmail.com>
Date: Sun, 6 Mar 2016 17:43:14 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CANaX5ne6s+q8tBRgt0WetC5z8R7C5Rc5-cqXB7frXQiSZ4WO9A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [RFC] Traits with interfaces
From: rowan.collins@gmail.com (Rowan Collins)

On 05/03/2016 23:15, Davey Shafik wrote:
> You are mid-reading, none of the classes in my examples extend the 
> others, they are all just using the same trait in different ways.
>
> - Class a: use the trait with no aliases. Result: as expected
> - Class b: use the trait with a simple alias, no visibility change. 
> Result: both methods


Right, the reason I was looking at inheritance was this line:

> ... and_will_  override inherited methods of the same name.


I misunderstood that the rest of the examples were also about how inheritance behaved.

> For the one you can't re-produce, it's class 'c', which is stand-alone
> here: https://3v4l.org/K9o6Y


Right, so this is actually consistent, because the resulting "stitched 
together" class looks like this:

class C {
public function bar() {}
private function bat() {}
}

Whereas when the alias wasn't private, it looked liked this:

class B {
public function bar() {}
public function bat() {}
}


You can actually change its visibility on one line and alias it on another:

class e {
     use foo {
         bar as private;
         bar as bat;
     }
}

https://3v4l.org/80gKF Stitched togorther, that gives you:

class e {
private function bar() {}
public function bat() {}
}


So the main confusion is that "bar as private bat" != "bar as private" + 
"bar as bat". :)

Regards,

-- 
Rowan Collins
[IMSoP]