Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54136
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <4E29A164.3070108@gmail.com>
References: <4E29949C.9020209@gmail.com> <CAKUjMCWWmhkQTMLoof76nFZEZs80cz4KFgKtw5UzsX6XwFMoVw@mail.gmail.com>
 <CAH8KiXK9z907NrPn4=v_P8iAUS+1NSMOXEe-nZpt1Mks43+YDw@mail.gmail.com> <4E29A164.3070108@gmail.com>
Date: Fri, 22 Jul 2011 09:18:27 -0700
Message-ID: <CADajX4Bipo6Syi_nG_+pbPzU=5Um2fdrxy8cCuZfyyXaniU7bA@mail.gmail.com>
To: Alex Howansky <alex.howansky@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] 5.4a2 trait attribute name conflict resolution
From: aharvey@php.net (Adam Harvey)

On 22 July 2011 09:12, Alex Howansky <alex.howansky@gmail.com> wrote:
>
>> That makes sense if it would overwrite the methods as well, but
>> otherwise it seems like it provides inconsistent functionality.
>
> Exactly. At the least, it's inconsistent. If it's a bug, then it seems the
> question becomes:
>
> Is the bug this:
>
> "Properties defined in a trait should be overridden by same-named properties
> defined in a class that use the trait."
>
> Or (as pointed out by Anthony) this:
>
> "You shouldn't be able to define properties in a trait."

Traits definitely need to be able to support properties, IMO, so I'd
say that the first behaviour just needs to be documented (and
potentially a notice added). Either the trait or the class is going to
have its property overwritten, so we should pick which definition wins
and go from there.

Adam