Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108254
To: Claude Pache <claude.pache@gmail.com>
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>
Thread-Topic: [PHP-DEV] [RFC] "use global functions/consts" statement
Thread-Index: AQHV1IfBuqjWnIu9lEWrxlRKvYFij6f9dXec
Date: Sun, 26 Jan 2020 21:37:26 +0000
Message-ID:
 <DM5PR07MB3067F716C9F0E6D5C2DB3D9DF9080@DM5PR07MB3067.namprd07.prod.outlook.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>,<A5AD5FD1-7CA1-49D9-86A0-D72EA08A84F5@gmail.com>
In-Reply-To: <A5AD5FD1-7CA1-49D9-86A0-D72EA08A84F5@gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [EPHj1zC1rVodRlLcVXt0I0nu/KBOfG6c]
x-ms-publictraffictype: Email
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 7ed1bdb3-d348-4beb-3531-08d7a2a7f007
x-ms-traffictypediagnostic: MW2NAM12HT230:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 hJpIQ5ezYE9xUSOYDn04sG6wM8TnAv2O8kwbJKp/2Ag8H0z2Qv+2DUXZc3AXZvW81qULn8LZiarTlRbQu42sQZUYBx13Hg0QjX4T4UGkIUHPWwQ29WL8fhLfu1W5a2PBgt6AC4Yy0gSZgGnGglj6GXKox/mHk6LXAvZ4PqQ3z02p9jxyLgz7Hf8qtTWwzz+4
x-ms-exchange-antispam-messagedata:
 FF03+IJDcVhyNgK2+5KeRDO0G3kl9OUv7RjW7Yoz46QTSucbFXymnAv8MsZvjY70rrHk/JsabBU1/uzvyHgpBphKpaU7Z3Es/Eqw/gaoUtNGZLbrOm86pfXz35OXeOOJWFOkwUo+8+Xiz5xOt4SX/A==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 7ed1bdb3-d348-4beb-3531-08d7a2a7f007
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jan 2020 21:37:26.5227
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2NAM12HT230
Subject: Re: [PHP-DEV] [RFC] "use global functions/consts" statement
From: tysonandre775@hotmail.com (tyson andre)

> and that you have to explicitly say that you use the current namespace fo=
r that name:=0A=
> =0A=
> <?php=0A=
> declare(function_and_const_lookup=3D'global');=0A=
> namespace MyNS;=0A=
> use function MyNS\foo;=0A=
> // or, equivalently: use function namespace\foo:=0A=
>=0A=
> function foo() { }=0A=
>=0A=
> foo(); // <-- this is the function defined just above=0A=
=0A=
That's a good solution to the ambiguity that I hadn't considered. Functions=
 and constants should be relatively uncommon for most projects, although I =
can see it getting repetitive for a file with dozens of constants.=0A=
(e.g. with namespace-scoped declares)=0A=
define() or declare(function_and_const_lookup=3D'global') should be adequat=
e workarounds.=0A=
- A subsequent RFC could reduce the restriction and make "const X =3D ..." =
always act as though it was immediately preceded by "use const X"=0A=
  This works better for constants than functions because constants can't be=
 declared anywhere but the top level.=0A=
=0A=
`use function namespace\foo;` is a syntax error, though. It can only be use=
d as `namespace\foo();`. It may be useful to add if projects adopt function=
_and_const_lookup, or other changes to namespace resolution get made.=0A=
=0A=
- Tyson=