Re: Re: Friend class/function
| From: | Andrea Faulds | Date: | Mon, 02 Nov 2015 11:03:05 +0000 |
| Subject: | Re: Re: Friend class/function | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-89035@lists.php.net to get a copy of this message | ||
Hi Rowan,
Rowan Collins wrote:
Andrea Faulds wrote on 01/11/2015 19:35:Yep, that would have worked, and that sounds like a much cleaner solution. Package/namespace visibility would solve a bunch of other use-cases too. Thanks! -- Andrea Faulds http://ajf.me/I recently wished PHP had this feature when trying to implement the Khronos Group Typed Arrays specification in PHP, which requires sharing certain data between unrelated (inheritance-wise) classes. I ended up having to expose a public method to get the data, but named in a way that was likely to deter use.Would "package" (namespace-based) visibility have solved the problem in this case? That's something I've often wanted - "this is public within this Lib, but should never be used outside it".