Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108252
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
In-Reply-To: <DM5PR07MB30677F5577E4C2105DF7B68EF9080@DM5PR07MB3067.namprd07.prod.outlook.com>
Date: Sun, 26 Jan 2020 21:32:35 +0100
Cc: Nikita Popov <nikita.ppv@gmail.com>,
 Nicolas Grekas <nicolas.grekas+php@gmail.com>,
 Mark Randall <marandall@php.net>,
 "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <A5AD5FD1-7CA1-49D9-86A0-D72EA08A84F5@gmail.com>
References: <DM5PR07MB3067B7578E3F04C5A20A221AF9210@DM5PR07MB3067.namprd07.prod.outlook.com>
 <CY4PR07MB30633FFAAF6E9CC45B3ECB43F9340@CY4PR07MB3063.namprd07.prod.outlook.com>
 <CAF+90c9svofd0rJV9ooDUb+rgsgE4+cbaahUnLzYqrksY+d=WA@mail.gmail.com>
 <DM5PR07MB3067239059A936661E1100B5F9340@DM5PR07MB3067.namprd07.prod.outlook.com>
 <DM5PR07MB3067A4F37F4D8E6738582859F9300@DM5PR07MB3067.namprd07.prod.outlook.com>
 <b8e7ced4-9cec-4bde-a009-622c477a0e58@DB3EUR04FT030.eop-eur04.prod.protection.outlook.com>
 <DM5PR07MB306711A0E8F1CADB23C17CB5F9300@DM5PR07MB3067.namprd07.prod.outlook.com>
 <CAF+90c-Rmmh3+iYqFmn1E+W5-S1qT4BpPhN9wgroz=9ZudeWpg@mail.gmail.com>
 <CAOWwgpkmawRgSJ2J8ZMoh_0MBskOgwJu-=HGJ42=6EQt+vz0Gw@mail.gmail.com>
 <DM5PR07MB30671C0F3103E927A1532B6CF90E0@DM5PR07MB3067.namprd07.prod.outlook.com>
 <CAF+90c8uCL85dVbLgapV2gOypFNBqocqvYWDB=JHKEmrq2JCwA@mail.gmail.com>
 <DM5PR07MB30677F5577E4C2105DF7B68EF9080@DM5PR07MB3067.namprd07.prod.outlook.com>
To: tyson andre <tysonandre775@hotmail.com>
Subject: Re: [PHP-DEV] [RFC] "use global functions/consts" statement
From: claude.pache@gmail.com (Claude Pache)

Hi,

I object to the following proposed behaviour, which is confusing:

<?php
declare(function_and_const_lookup=3D'global');
=20
namespace MyNS;
=20
function sprintf($msg, ...$args) {
    // this and remaining statements still refer to \sprintf, not =
MyNS\sprintf
    return sprintf("Prefix $msg", ...$args);
}
?>

I think we can do better, following the example of what we have today, =
namely: Currently, the following triggers a fatal error:

<?php
namespace MyNS;
use function OtherNS\foo;

function foo() { }
// Fatal Error: Cannot declare function MyNS\foo because the name is =
already in use
?>

Therefore I suggest that the following be an error:

<?php
declare(function_and_const_lookup=3D'global');
namespace MyNS;

function foo() { }
// Fatal Error: Cannot declare function foo because the name refers is =
in the global namespace

?>

and that you have to explicitly say that you use the current namespace =
for that name:

<?php
declare(function_and_const_lookup=3D'global');
namespace MyNS;
use function MyNS\foo;
// or, equivalently: use function namespace\foo:

function foo() { }

foo(); // <-- this is the function defined just above

?>

=E2=80=94Claude=