Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46667
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.78.25 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=Nn5guQ2Sbv5guwX+1oH4O0lwBrlXZBH3O5pm0zAa15r4gELAWjl3k4Hae1sQqj9Dp5
         RPArTmIuxBCMlPbuLXd9eUUm4opGSyZWl9Lprt/1p5uJHIGGlOZ1yIo/3KILVqzifsBq
         NT4nT96YBOOw17DZz9WprDUS2LDOjPk497toM=
MIME-Version: 1.0
In-Reply-To: <c25f8d341001121811w29b56ef0v4ad43c66e7667c25@mail.gmail.com>
References: <BF.85.26332.88E6B4B4@pb1.pair.com>
	 <e666c3891001111729n7294ef23la55b02272044662e@mail.gmail.com>
	 <3A.94.26332.3E9EB4B4@pb1.pair.com>
	 <c25f8d341001111932o3a0f28e8w27985700c6684454@mail.gmail.com>
	 <e2e02fe1001121440l4c893a3chfd67c0173f567d56@mail.gmail.com>
	 <c25f8d341001121809w4640c98as273603ef758384d5@mail.gmail.com>
	 <68de37341001121810x10be424fu842402a398d3709e@mail.gmail.com>
	 <c25f8d341001121811w29b56ef0v4ad43c66e7667c25@mail.gmail.com>
Date: Tue, 12 Jan 2010 21:29:41 -0500
Message-ID: <68de37341001121829p3a2f6a62y6eb2a45863e62ae6@mail.gmail.com>
To: mm w <0xcafefeed@gmail.com>
Cc: Chris Stockton <chrisstocktonaz@gmail.com>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] __toString(), __toArray()
From: oorza2k5@gmail.com (Eddie Drapkin)

What you're proposing is just forcing __call, _callStatic, __get and
__set into a single method, which does nothing to reduce the amount of
magic, only obfuscate it.  And it certainly offers no alternative to
"__cast", at least not that I can see.

On Tue, Jan 12, 2010 at 9:11 PM, mm w <0xcafefeed@gmail.com> wrote:
> the multiplication of magic, the pointed point, need to read more careful=
ly
>
> On Tue, Jan 12, 2010 at 6:10 PM, Eddie Drapkin <oorza2k5@gmail.com> wrote=
:
>> How does this have *anything* to do with the discussion at hand?
>>
>> On Tue, Jan 12, 2010 at 9:09 PM, mm w <0xcafefeed@gmail.com> wrote:
>>> don't worry it's only for people who are working with MVC and
>>> RootObject structure, there is too much magics already and __cast is
>>> not needed at all,
>>> as we cannot monkey patch to add an observer on itself, a nice
>>> solution should have a catchable object so __catch any calls
>>>
>>> function __catch($data, $type) {
>>> =C2=A0 =C2=A0if (method =3D=3D $type) {
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (data[selector] =3D 'setValue' && observ=
edValueForKeyPath) {
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 $this->_setValue(($data['arg'=
]);
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 return;
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 }
>>> =C2=A0 =C2=A0}
>>> =C2=A0 =C2=A0continue_natural_call();
>>> }
>>>
>>> we could imagine to have a root-object-built-in-class that is
>>> naturally observable, or a root classObject at all, anyway it's only
>>> something for people who are doing OO programming,
>>> so don't worry
>>>
>>> On Tue, Jan 12, 2010 at 2:40 PM, Chris Stockton
>>> <chrisstocktonaz@gmail.com> wrote:
>>>> Hello,
>>>>
>>>> On Mon, Jan 11, 2010 at 8:32 PM, mm w <0xcafefeed@gmail.com> wrote:
>>>>> cast is not needed in PHP
>>>>>
>>>>> i 'd rather be more interesting in
>>>>>
>>>>> class Obj {
>>>>> =C2=A0 =C2=A0 function __catch($data, $type) {
>>>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0//$type [ static_method, met=
hod, get_property, set_property]
>>>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if (observed && =C2=A0$type =
=3D=3D set_property && somevalueIsObserved) {
>>>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0$observ=
er->notify("somevalue::valueWillChanged");
>>>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0$this->=
somevalue =3D $data['somevalue'];
>>>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0$observ=
er->notify("somevalue::valueDidChanged");
>>>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0} else {
>>>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0continu=
e__call();
>>>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0}
>>>>> =C2=A0 =C2=A0 }
>>>>> }
>>>>
>>>> What? ...
>>>>
>>>>>> Etienne Kneuss wrote:
>>>>>> This is where operator over-loading would be useful however perhaps =
only
>>>>>> explicit casts would make sense here.
>>>>
>>>> I beleive adding a __cast(string $type) would be a useful feature for
>>>> me, very often I have a toArray method defined. I agree with you that
>>>> due to unexpected edge cases with operator precedence and general type
>>>> juggling that __cast should only be called on explicit (cast).
>>>>
>>>> I.E.:
>>>> class Int { public function __cast($type) { return 'int' =3D=3D $type =
? 15 : 0; } }
>>>> $r =3D new Int;
>>>>
>>>> var_dump($r + 1); // 2
>>>> var_dump((int) $r + 1); // 16
>>>> var_dump((bool) $r + 1); // 1
>>>>
>>>
>>> --
>>> PHP Internals - PHP Runtime Development Mailing List
>>> To unsubscribe, visit: http://www.php.net/unsub.php
>>>
>>>
>>
>