Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64919
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zerocue.com designates 67.200.53.250 as permitted sender)
Message-ID: <50F2C7D8.3040508@zerocue.com>
Date: Sun, 13 Jan 2013 08:42:32 -0600
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Mark <markg85@gmail.com>
CC: Stas Malyshev <smalyshev@sugarcrm.com>, 
 Nikita Popov <nikita.ppv@gmail.com>,
 PHP Developers Mailing List <internals@lists.php.net>
References: <50E41BB6.4030901@zerocue.com> <50E648BE.2060005@zerocue.com> <50E6822D.9060807@sugarcrm.com> <71B3F435-4289-473B-B4D7-EB2DB5F888A9@zerocue.com> <7213E637-26A2-4F44-82DE-297E751726CD@zerocue.com> <50E6F501.4090806@zerocue.com> <50E75658.6050006@sugarcrm.com> <50E79D16.1090905@zerocue.com> <CAF+90c9HRNGQBP1j6pWcEoKJTF9hjpXTHQ2Egnj2WBBc37Uw2Q@mail.gmail.com> <50EF56BD.3040608@sugarcrm.com> <CAF+90c9qFNHk7nev-OsnkCjRKCyvm=XgczY9ViS0tknZ9Q6qYA@mail.gmail.com> <50EFBA6F.90702@sugarcrm.com> <CAPd6JnGLyEH=b1o0+pXk8kJOE-2tTXrNWKB3Sr6AvGG=K1OSYw@mail.gmail.com>
In-Reply-To: <CAPd6JnGLyEH=b1o0+pXk8kJOE-2tTXrNWKB3Sr6AvGG=K1OSYw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [PHP-RFC] Property Accessors 1.2 : parent::$foo Issue
From: cpriest@zerocue.com (Clint Priest)


On 1/13/2013 8:01 AM, Mark wrote:
> I'm guessing this RFC won't make it in PHP 5.5? Too bad since it did
> seem like a very nice feature to have.
>
> I don't know if it is very helpful but posting nevertheless. I'm a
> C++/Qt/QML/PHP developer and for me the proposed syntax in the v1.2
> document makes perfect sense and is intuitive to use. As for the
> earlier example about isset...
>
> i'd expect an example like this:
>
> class SomeClass {
>      public $date {
>          get;
>          set(DateTime $date);
>      }
> }
>
> $temp = new SomeClass();
> i'd expect "isset($temp->date)" to return exactly the same as if the
> class where defined like this:
>
> class SomeClass {
>      public $date;
> }
That's correct, it will.

Furthermore, isset() will never throw an error, even if it would not be 
legal to call isset or get (from 1.1 RFC changes).
> I don't know if that issue was already sorted out but i wanted to
> share my expectations in that regards.
>
> Will this make PHP 5.5? Or will it be deferred to 5.6?
Nikita, Stas and I are working very hard to make it into 5.5, we expect 
to propose a vote sometime in the next couple of days.

** Any remaining feedback is appreciated, the RFC is being kept up to 
date w/ current understood consensus. **

-- 
-Clint