Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64539
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: <50E79E98.8090209@zerocue.com>
Date: Fri, 04 Jan 2013 21:31:36 -0600
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Stas Malyshev <smalyshev@sugarcrm.com>
CC: Nikita Popov <nikita.ppv@gmail.com>, 
 PHP internals <internals@lists.php.net>
References: <CAF+90c_girfbcPBb8rCV3bPNR2Hsd5gyRPB+VArCfqjPPqG5DQ@mail.gmail.com> <CAFMT4Np7knN1xS+wmeS=4ToVDZ2hryCd8K1yOUox+ubVoaX=Hg@mail.gmail.com> <50E6F2EB.20108@zerocue.com> <50E757E1.8060803@sugarcrm.com>
In-Reply-To: <50E757E1.8060803@sugarcrm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Alternative typehinting syntax for accessors
From: cpriest@zerocue.com (Clint Priest)


On 1/4/2013 4:29 PM, Stas Malyshev wrote:
> Hi!
>
>> This shouldn't be an issue because it is not possible to set the
>> property without going through the setter, which would be a type hinted
>> accessor function.
> It is possible, if this property's guard is set. Since guard works for
> all code called from inside the setter, if setter is doing something not
> trivial (meaning, calls any functions, explicitly or implicitly) it is
> possible to set the property directly. Since the value you are getting
> is defined by the getter, there are no guarantees there too. So
> effectively, unless both getter and setter are implicit, this does not
> give you anything compared to the typed setter.
I think I was referring to the possibility I mentioned in another email 
about a second call to a getter which was already guarded would return 
NULL and likewise a second call to a setter which was already being 
guarded would do whatever __set() does...?  Ignored?

-- 
-Clint