Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97257
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPhkiZx3AdHs9mGG2=kuBgdmcsyH827ETSkUXXYE--fqhhr6cw@mail.gmail.com>
References: <CAAn=CzXJTy4e7sRtFiXM-RtY8iwx2xu3bDZTgy=Ge7dRUc6XdA@mail.gmail.com>
 <CAAn=CzXDAmJHhmYZ6p5g+6a-i7RnEk_COA0dze=d5gvBBrxeig@mail.gmail.com>
 <CAAn=CzXjy7OECAHO29vNfPrSGjrcQ1Dx1hCObHmXJskQ+zG9Tg@mail.gmail.com>
 <CAPhkiZxXpeMrxDzrSOwEKkTCtVCphdgO1fMSwavfgcU6KQONkw@mail.gmail.com>
 <CAAn=CzVwEMwWxOnWK7t4cDD4o30zxMbpqV5QAbJ9ZQQ=9rx27Q@mail.gmail.com> <CAPhkiZx3AdHs9mGG2=kuBgdmcsyH827ETSkUXXYE--fqhhr6cw@mail.gmail.com>
Date: Fri, 2 Dec 2016 14:51:40 +0000
Message-ID: <CAAn=CzVcxgcRebuvLg1syrkVwmXPi=XkoTW4L7xLv_-Hj3Chnw@mail.gmail.com>
To: Andrey Andreev <narf@devilix.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c3ae5e71b9c10542ae13c5
Subject: Re: [PHP-DEV] Re: [Concept] Magic Casting
From: bowersbros@gmail.com (Alex Bowers)

--001a11c3ae5e71b9c10542ae13c5
Content-Type: text/plain; charset=UTF-8

Damn. I must have done that to a lot of emails. Gonna have to resend them
all when I get home. Sorry folks for dupes.

On 2 December 2016 at 14:46, Andrey Andreev <narf@devilix.net> wrote:

> Hi again,
>
> On Fri, Dec 2, 2016 at 4:19 PM, Alex Bowers <bowersbros@gmail.com> wrote:
>
>> I don't see how the interface is equivalent.
>>
>> The benefit of this, is that you can convert types passed into a method
>> to the type you expect automagically, Castable wouldn't allow that, only a
>> new magic method (or reflection and user land code possibly?) would allow
>> this.
>>
>
> A magic method is essentially an implicit interface ...
> The interface itself does nothing. But when it is implemented, the engine
> will know that the class constructor is public and accepts a single
> parameter - thus, also knowing that it could try to do a new
> ClassName($yourParameterHere)
>
>
>>
>> As for the limitation of only one parameter being accepted, what would
>> the other possible parameters be?
>>
>> Since this is based entirely on the casted variable, there can only
>> possibly be one variable there, the one passed into that position in the
>> functions arguments.
>>
>>
> What I meant is - you cannot cast to a class that requires more than one
> dependency to be instantiated - that's the obvious limitation.
>
>
>> Arguably, this feature would resolve some bugs in peoples code, because
>> it can allow better enforcing of types.
>>
>
> It enables magic behavior, that's the opposite of enforcement ... If you
> want to enFORCE something, you force the developer to do something, you
> don't auto-magically do the thing for them.
>
> P.S.: I suppose you've hit "Reply" instead of "Reply All"? I was the only
> recepient of the message I'm quoting.
>
> Cheers,
> Andrey.
>
>

--001a11c3ae5e71b9c10542ae13c5--