Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60229
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.45 as permitted sender)
MIME-Version: 1.0
Sender: patrick.allaert@gmail.com
In-Reply-To: <4F910311.7040406@sugarcrm.com>
References: <9570D903A3BECE4092E924C2985CE485546B0737@MBX202.domain.local>
	<4F910311.7040406@sugarcrm.com>
Date: Fri, 20 Apr 2012 12:35:32 +0200
Message-ID: <CACwt+Jc_TK8=X27fkdsF18nj3kmQ_zN5MBz29W+-eQUT6=gQEw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Clint M Priest <cpriest@zerocue.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] RFC: Property get/set syntax
From: patrickallaert@php.net (Patrick ALLAERT)

2012/4/20 Stas Malyshev <smalyshev@sugarcrm.com>:
> How these would work with isset - what !empty($this->Hours) return? What
> would happen if you do unset($this->Hours)? What happens if you do
> $this->Hours++ or sort($this->Hours) (assuming $Hours is an array)?
> These things need to be defined in the RFC too.

My suggestion is to support the same methods for properties as we do
for magic class methods: __set, __get, __isset and __unset.
All the other operations (sort, ++, <<,...)  should behave exactly as
if it was be implemented with current magic class methods with a usual
switch/case statement.