Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63646
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mrclay.org from 50.22.11.19 cause and error)
Message-ID: <508A93CA.4030507@mrclay.org>
Date: Fri, 26 Oct 2012 09:44:42 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: internals@lists.php.net
References: <508A67E6.2000405@zerocue.com>
In-Reply-To: <508A67E6.2000405@zerocue.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Property Accessors v1.2 : Internal Accessor Method
 Visibility / Callability
From: steve@mrclay.org (Steve Clay)

On 10/26/12 6:37 AM, Clint Priest wrote:
> https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented/change-requests
> ------------------------------------------------------------------------
> Some people are in favor of the internal functions being generated by an accessor
> declaration should be invisible and non-callable directly. Others are in favor of leaving
> them visible and callable.

If we leave them callable,

* What would be the effects of users defining the "internal" methods (in both cases of 
if/if not the accessor is also defined)? Considering current magic methods are 
*purposefully designed* to be implemented by the user, I expect users to try this and, if 
it works, release code with it.

* I assume one could use them as regular methods?
    * call_user_func([$foo, '__getpropName']);
    * $foo->{"__get$propName"}

I apologize if these were already covered.

Steve Clay
-- 
http://www.mrclay.org/