Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63641
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: <508A68B9.1050801@zerocue.com>
Date: Fri, 26 Oct 2012 05:40:57 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative;
 boundary="------------050603030509050809070103"
Subject: [PHP-DEV] [RFC] Property Accessors v1.2 : isset / unset "failable"
From: cpriest@zerocue.com (Clint Priest)

--------------050603030509050809070103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I'm opening up several new threads to get discussion going on the 
remaining "being debated" categories referenced in this 1.1 -> 1.2 
change spec:
https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented/change-requests

------------------------------------------------------------------------
*isset / unset / attempted writes when no setter / attempted reads when 
no getter**
*
Stas suggested that since there is presently no cases where these can 
fail that with accessors these should never "fail."

Three possible ways to go (maybe others):

 1.      If all cases can be tested for during compilation, prefer
    compile failures.
 2.      Let the compilation occur and at runtime when a disallowed
    action is attempted, emit a warning and move on.
 3.      As is currently, either at compilation or at runtime we issue a
    fatal error and stop execution (probably least preferable if at runtime)

If "no failures" should be the way we want to go, then #2 or some 
derivative makes the most sense.
------------------------------------------------------------------------

Thoughts?

-- 
-Clint


--------------050603030509050809070103--