|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #55331 Package/Namespace visibility control keyword
Submitted: 2011-07-31 21:42 UTC Modified: 2018-05-05 21:15 UTC
Avg. Score:4.7 ± 0.5
Reproduced:31 of 31 (100.0%)
Same Version:8 (25.8%)
Same OS:14 (45.2%)
From: gordon dot mcvey at ntlworld dot com Assigned:
Status: Duplicate Package: Class/Object related
PHP Version: 5.4.0alpha2 OS: any
Private report: No CVE-ID: None
 [2011-07-31 21:42 UTC] gordon dot mcvey at ntlworld dot com
With the addition of namespaces, a new level of member protection for classes similar to Java's package visibility would be a useful addition.  

Currently we have the following protection levels: 

* Private: Member is visible only within the class that defines it
* Protected: Member is visible within the class that defines it and any subclasses that inherit from it
* Public: Member is visible anywhere.  

I would suggest that an additional "package" or "namespace" protection level keyword would be a useful addition.  Members marked as package or namespace would be visible to any other class defined in the same namespace as the defining class.  


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2012-04-05 09:57 UTC] info at strictcoding dot co dot uk
This would be awesome. It's currently very difficult to protect a domain model 
without this feature.
 [2013-04-05 20:22 UTC] edp at ultradrive dot com
As in Java, the package access level should be implemented both for entire classes and for individual members in a class.
 [2014-05-08 21:26 UTC] i_am_vib at yahoo dot com
Any news regarding this feature?
 [2015-08-11 09:34 UTC] tom at r dot je
I was about to post this exact request.

 This is currently handled by annotations and flagging the method as @api or @internal (see and ) which are used to denote whether third parties should call the methods or not.

The reason for this is simple: It allows package authors to break BC on the methods (or remove them entirely) safe in the knowledge that it won't break third party code because the only place their being called from is the same project.

In Java this is handled by the 'protected' keyword which allows any method in the same package to call a method flagged as 'protected'. 

I'd also like to see a 'package' (or 'namespace', or another word) visibility that mimics this functionality. To make it sensible and actually useful it should be anything in the same root namespace. Example code:


namespace Foo\Bar;
class X {
  package function y() {

namespace Foo\Whatever;
class Y {
   public function __construct() {
        $x = new \Foo\Bar\X;
        $x->y(); //ALLOWED


namespace Another\Project\Entirely;
class Y {
   public function __construct() {
        $x = new \Foo\Bar\X;
        $x->y(); //NOT ALLOWED

 [2018-05-05 21:15 UTC]
-Status: Open +Status: Duplicate
 [2018-05-05 21:15 UTC]
Duplicate of request #52297
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Tue Sep 28 05:03:38 2021 UTC