Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50702
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 76.96.30.40 cause and error)
Message-ID: <4CF3ED92.3010401@garfieldtech.com>
Date: Mon, 29 Nov 2010 12:14:42 -0600
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: internals@lists.php.net
References: <ae7aa0536c47a2ac725222d49918183f.squirrel@webmail.basnetworks.net> <003601cb8fd0$f6494e80$e2dbeb80$@com> <4CF3B855.5010406@sugarcrm.com> <003401cb8fee$1be39840$53aac8c0$@com>
In-Reply-To: <003401cb8fee$1be39840$53aac8c0$@com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: C-sharp style property get/set syntax for PHP
From: larry@garfieldtech.com ("larry@garfieldtech.com")

On 11/29/10 11:51 AM, Jonathan Bond-Caron wrote:

> Right, it looks the same but the subtle difference is 'property Hours'
> wouldn't be registered as a class. It's just container code for get(), set()
> methods that would get 'compiled' into opcodes in the class TimePeriod (the
> property exists vs. searching for it in runtime). So you can think of it as
> a special 'trait' that only applies to properties.
>
> The idea behind this syntax is you can move the 'property' definition out of
> the class so that you can test and re-use it somewhere else (like traits).
>
> That might not be problem if you can define properties in traits (needs to
> be explained in the RFC):

I think I'd prefer to use Traits for externally-defined properties 
rather than defining a new top-level construct.  It's fewer moving parts 
and we don't need to figure out how autoloading would be affected. 
(Autoload would work the same way it does now for traits... whatever 
that is.)

That would then imply we do need to be able to declare the existence of 
a property and whether it has get, set, or both independently of the 
definition, just like methods, so that we can have a proper 
interface/trait split for properties just as for methods.

--Larry Garfield