Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43729
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error)
Message-ID: <E98065374DA64A1D8602A3A442BF6BED@pc>
To: <internals@lists.php.net>
References: <e52c06b30904150713s7cb13e3ele4b075cbe803fb82@mail.gmail.com> <52F25C37-F12D-4A85-A7D3-C579637B56C5@stefan-marr.de> <e52c06b30904171020r390a042ar42582acf9ca7b082@mail.gmail.com> <3B04560F-97DC-423D-8606-3436F28EF2D1@stefan-marr.de>
Date: Sat, 18 Apr 2009 20:27:03 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="ISO-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Grafts, Traits, horizontal reuse
From: sv_forums@fmethod.com ("Stan Vassilev | FM")

> The question here is how to handle property accesses, in particular 
> accesses to unspecified properties.
> I actually would expect to have a lookup mechanism which first looks  in 
> the trait, and if the property is not found there, its going to the 
> object. I expect this behavior, because it is similar to what we have 
> with inheritance and properties defined by a superclass.
>
> If a property is not jet defined, I would expect it to be created in  the 
> most inner scope, like local variables.
> On the other hand, I also would expect, as in inheritance, properties  to 
> be found defined by super classes, or the class which defines the 
> composition.
>
> But this only my intuitive solution, so this could of course be  specified 
> different.
>
> Best regards
> Stefan

Hi,

I see this in a much simpler fashion. Treat traits as a preprocessor step 
semantically.

Internally, trait methods on multiple classes may point to the same method 
to save resources, but in my opinion there's no need to complicate matter by 
introducing new resolution rules, scopes, and so on.
The way I see it:

1) Property/Method name conflicts on trait/class, within the class including 
the trait raises Fatal Error.
2) Extending classes can override the property/method, unless it's a final 
method, just like as if they override normal parent class property/method.
3) There's a single space for a class property and its trait properties, so 
access works as if it was all class properties.

Feedback?

Regards,
Stan Vassilev