Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91496
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender)
To: internals@lists.php.net
References: <CAF8MkRhYJZApgQbr16DmDdFxET9ORkah9jxabL7nbHFKYh0N1A@mail.gmail.com>
 <94.96.08749.188B8D65@pb1.pair.com>
 <CANaX5nfHALhKJcf2B46sz0hc5gDu+dY7J_kD17SM=MXH4hLvqg@mail.gmail.com>
Message-ID: <56D95E18.9020007@gmail.com>
Date: Fri, 4 Mar 2016 10:06:16 +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: <CANaX5nfHALhKJcf2B46sz0hc5gDu+dY7J_kD17SM=MXH4hLvqg@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------080605010600000701070407"
Subject: Re: [PHP-DEV] Re: [RFC] Traits with interfaces
From: rowan.collins@gmail.com (Rowan Collins)

--------------080605010600000701070407
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Davey Shafik wrote on 04/03/2016 07:17:
> 1. If you simply alias (use foo { bar as bat; }) then you end up with an
> *additional*  method with the new name, the trait method as defined is still
> brought in, and_will_  override inherited methods of the same name.

Here's a clearer example of this: https://3v4l.org/RKHPt

Unfortunately, you can't even use "insteadof" to directly bring the 
parent method back in [https://3v4l.org/qOS5T], but you can stub it out 
with a direct call to parent:: [https://3v4l.org/s9i4N].

> 3. Doing this (visibility + name)_only_  gives you the new method, which is
> _different_  behavior to #1

I can't reproduce this: if I say "bar as private bat", the trait's bar 
still shows up, and is public, just as in the previous example: 
https://3v4l.org/1jH6o

Your examples are rather confusing because they are effectively applying 
the same trait twice, at different levels of the hierarchy; I'm not sure 
this is a particularly likely scenario, or relevant to how interfaces 
should behave.

Regards,
-- 
Rowan Collins
[IMSoP]

--------------080605010600000701070407--