Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89622
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAKws9z0jn0crpYntxNiKWEU-tLdATJCATpC6Vk+jouVJbzSBFA@mail.gmail.com>
References: <CAKws9z0jn0crpYntxNiKWEU-tLdATJCATpC6Vk+jouVJbzSBFA@mail.gmail.com>
Date: Fri, 4 Dec 2015 11:52:44 -0500
Message-ID: <CAAyV7nGHRQyNA7NXY==_4uLGM5dRnoOU6WNBfFKhLjx5BvYrtA@mail.gmail.com>
To: Scott Arciszewski <scott@paragonie.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Namespaces
From: ircmaxell@gmail.com (Anthony Ferrara)

Scott,

On Fri, Dec 4, 2015 at 11:26 AM, Scott Arciszewski <scott@paragonie.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?
>
> https://3v4l.org/po925
>
> Scott Arciszewski
> Chief Development Officer
> Paragon Initiative Enterprises <https://paragonie.com>

It's not a bug. It's explicit. The `\` prefix says it's a global
function. The non-prefixed looks in the current namespace and then
falls back to global.

Also, in PHP 5.6+ you can do something slightly different to achieve
the same result: use function.

namespace Foo {
    use function random_int;
    var_dump(random_int(1, 100));
    var_dump(\random_int(1, 100));
}

That will always behave the same no matter if someone defines a
namespace-specific random_int function, it will always use the global
version.

https://3v4l.org/cR6Gg

This actually opens a pretty interesting edge-case, where you can
define a function in the namespace and use the global one without
needing a "\".

namespace Foo {
    use function strlen;
    function strlen(string $str) : int {
        return strlen($str) + 1;
    }
}

That actually is not recursive. This is a bit non-obvious, but
completely follows the rules set forth. So I don't think there's a bug
(though we may want to raise a notice in that collision case)...

Anthony