Re: Fix for #53727 (is_subclass_of resolution with interfaces)
| From: | Benjamin Eberlei | Date: | Wed, 29 Jun 2011 21:00:52 +0000 |
| Subject: | Re: Fix for #53727 (is_subclass_of resolution with interfaces) | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-53680@lists.php.net to get a copy of this message | ||
On Wed, 29 Jun 2011 22:22:54 +0200
David Zülke <david.zuelke@bitextender.com> wrote:
> On 29.06.2011, at 22:20, Paul Dragoonis wrote:
>
> > On Wed, Jun 29, 2011 at 8:49 PM, Ralph Schindler <ralph@smashlabs.com> wrote:
> >> Correct.
> >>
> >> I was hasty in that example, the first was copied & tested (and is reflected
> >> in the test, as is that variation of what I wrote up.)
> >>
> >> Either way, test and patch work in 5_3.
> >
> > Doesn't this functionality confuse matters?
> >
> > If this patch is added, is there now no difference between instanceof
> > and is_subclass_of(). If this is the case my question is then why do
> > we have two methods to do the same thing?
> >
> > I thought instanceof was for parent classes + interfaces.. and
> > is_subclass_of() was just for parent classes.
>
> instanceof is a language construct and only operates on object instances.
>
> David
>
>
plus there is a difference if $a is a User is_subclass_of($a, 'User') returns false, $a
instanceof User returns true.