Re: Namespaces
| From: | Scott Arciszewski | Date: | Fri, 04 Dec 2015 19:28:01 +0000 |
| Subject: | Re: Namespaces | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-89629@lists.php.net to get a copy of this message | ||
Stanislav, Anthony:
Okay, I just wanted to make sure I wasn't overlooking an unintended
behavior. I'm going to continue using \explicit_prefixing().
http://userjac.com/wp-content/uploads/2014/05/haters-gonna-hate-cool-dog.jpg
Scott Arciszewski
Chief Development Officer
Paragon Initiative Enterprises <https://paragonie.com>
On Fri, Dec 4, 2015 at 2:24 PM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:
> Hi!
>
> > It has been brought to my attention that my consistent use of \ prefixing
> > of global functions is an eyesore, but I've got a simple little PoC that
> > shows why I do it, and now I'm wondering if the behavior I'm working
> around
> > should qualify as a PHP bug?
>
> No, it's not a bug, it is a feature. You can override function in a
> namespace. It's still not a reason to mark every function you are not
> overriding with \. Unless, of course, you are importing foreign (as, not
> controlled by you) code into your namespace, in which case I think
> that's where the problem lies.
> --
> Stas Malyshev
> smalyshev@gmail.com
>