Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108197
To: Mark Randall <marandall@php.net>, "internals@lists.php.net"
	<internals@lists.php.net>
Thread-Topic: [PHP-DEV] Re: [RFC] "use global functions/consts" statement
Thread-Index:
 AQHVwNgGtev425C1jEaW2/fYCDQJoKfqjUCogAA6vwCAABZSCIAF7qHQgAA+1YCAABKbIg==
Date: Sat, 18 Jan 2020 22:53:22 +0000
Message-ID:
 <DM5PR07MB306711A0E8F1CADB23C17CB5F9300@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>
In-Reply-To:
 <b8e7ced4-9cec-4bde-a009-622c477a0e58@DB3EUR04FT030.eop-eur04.prod.protection.outlook.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [crcx/p/5C6FPi9k7z3NsWp3d9rdBbuGx]
x-ms-publictraffictype: Email
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 91d84ba7-770b-4a43-a091-08d79c69386c
x-ms-traffictypediagnostic: BN7NAM10HT201:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 9qKRBoAC0WOi9avw3E4ztRIayg7iizZRx6C5sXgfNNNILUYHMKMrTXiuBO2ofTvGkMOG62oTqTt7NFICNoaPFjLk0+9aFdkz1RTNwaJIui90edqdCFFj1LJTeefkRatvaxGnrYdo8AklBguwSZXc8+T5GAeGZKuCJR2b41P8xz+/D817b67oUXKuy1KPqI/LfbhRVJ5LJl0WUE8MlcA9mFyY2PoV649kaIQoPoQ3OIA=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="Windows-1252"
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: 91d84ba7-770b-4a43-a091-08d79c69386c
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jan 2020 22:53:22.6117
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7NAM10HT201
Subject: Re: [PHP-DEV] Re: [RFC] "use global functions/consts" statement
From: tysonandre775@hotmail.com (tyson andre)

> I'd much rather have something like:=0A=
>=0A=
> declare(ambiguous_element_lookup=3D0)=0A=
> =0A=
> declare(ambiguous_element_lookup=3Doff)=0A=
=0A=
Aside: declare(unambiguous_element_lookup=3D1) is probably a better choice =
than my first choice of (disable_ambiguous_element_lookup=3D1), but probabl=
y not the best choice.=0A=
=0A=
> I find that the =93disable_ambiguous_element_lookup=94 directive name is,=
 well, ambiguous.=0A=
> Does it mean that it will look up only in the current namespace, or only =
in the global namespace? I can=92t guess.=0A=
> =0A=
> Maybe a three-value directive:=0A=
> =0A=
>    declare(function_and_const_lookup=3Dglobal);=0A=
>    declare(function_and_const_lookup=3Dnamespace);=0A=
>    declare(function_and_const_lookup=3Dfallback); // the default=0A=
=0A=
That's my favorite setting name overall so far - it ends up being as long a=
s disable_ambiguous_element_lookup and more self-explanatory.=0A=
I don't plan to include namespace-only in the RFC - future RFCs could propo=
se additional values independently.=0A=
=0A=
Probably just `=3D global` and `=3D default`, because the default might eve=
ntually change (from the fallback),=0A=
and =3D fallback could be added if the old fallback was desirable enough.=
=0A=
- `=3D default` would only be useful to set resolution back to the default=
=0A=
  with future language changes such as https://wiki.php.net/rfc/namespace_s=
coped_declares#implementation_considerations=0A=
=0A=
> "namespace_lookup"=0A=
=0A=
It might cause confusion when a new php programmer tries to set this settin=
g,=0A=
and discovers that catch(Exception) {} still means MyNS\Exception with decl=
are(namespace_lookup=3Dglobal).=0A=
(assuming you meant something along those lines)=