Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63434
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 207.97.245.153 as permitted sender)
Message-ID: <507D1A55.7060301@sugarcrm.com>
Date: Tue, 16 Oct 2012 11:27:01 +0300
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= <johannes@schlueters.de>
CC: Clint Priest <cpriest@zerocue.com>, 
 "internals@lists.php.net" <internals@lists.php.net>
References: <9570D903A3BECE4092E924C2985CE485612B3B48@MBX202.domain.local> <1349828182.18939.31.camel@guybrush>
In-Reply-To: <1349828182.18939.31.camel@guybrush>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Propety Accessors v1.1
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> The RFC states
>         ReflectionClass::getMethods() will not return accessor functions
>         (hides implementation detail).
> Up until now reflection is leaky and is telling the truth. We should
> either keep that or completely clean up reflection. (mind also
> get_class_methods() and such)

I think the reflection should return all methods that exist. If the
accessors are implemented as PHP methods/functions (and I see no reason
why not) then reflection should return it. Reflection, as you pointed
out, should tell the truth. There's nothing "leaky" about it, IMO - yes,
it's an implementation detail, so what? If you don't want to use
implementation details, don't - just ignore all __ functions and don't
call them. Python, for example, has tons of __ functions, and people
live just fine with it.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227