Re: Re: Ambiguity in the oop5 visibility docs

From: Date: Fri, 25 May 2018 23:00:48 +0000
Subject: Re: Re: Ambiguity in the oop5 visibility docs
References: 1 2 3 4  Groups: php.doc php.internals 
Request: Send a blank email to internals+get-102137@lists.php.net to get a copy of this message
That's not really a bug, that's expected behaviour on which stuff like friend classes and entire libraries are based upon... On Fri, 25 May 2018, 20:50 Pedro Magalhães, <mail@pmmaga.net> wrote: > On Fri, May 25, 2018 at 6:47 PM, Rowan Collins <rowan.collins@gmail.com> > wrote: > > > > I'm not sure what exactly is "ambiguous" or "might change" here. > > The > > current text accurately describes what "protected" means in PHP, and in > > many other languages: a property which may be accessed only within the > > current class, classes inheriting from it, and classes from which it > > inherits. > > > I think that what the note may be referring to is the fact that currently, > a child class can access the protected members of another child class if > this member was declared on the parent class. > However, this is a bug as described on > https://bugs.php.net/bug.php?id=50892 > which hasn't been fixed yet as the potential BC break makes it more > suitable for a major version. > > Regards, > Pedro >

« previous php.internals (#102137) next »