Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108279
To: Rowan Tommins <rowan.collins@gmail.com>, "internals@lists.php.net"
	<internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC] "use global functions/consts" statement
Thread-Index: AQHV1IfBuqjWnIu9lEWrxlRKvYFij6f9dXecgADKhQCAAFMdqIAAWbgAgABUv10=
Date: Tue, 28 Jan 2020 01:06:36 +0000
Message-ID:
 <DM5PR07MB3067ACE4E99E69B276DD8E5CF90A0@DM5PR07MB3067.namprd07.prod.outlook.com>
References:
 <DM5PR07MB3067B7578E3F04C5A20A221AF9210@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>
 <DM5PR07MB3067F716C9F0E6D5C2DB3D9DF9080@DM5PR07MB3067.namprd07.prod.outlook.com>
 <CAF+90c8sBcWnsZxMQNgOccHeVbDnhHmjbbRuCzO8QD9oJZA6jA@mail.gmail.com>
 <DM5PR07MB30675BDFD91C54AAF45E9261F90B0@DM5PR07MB3067.namprd07.prod.outlook.com>,<dace510b-46c0-8b06-ca8b-5159f90af1a6@gmail.com>
In-Reply-To: <dace510b-46c0-8b06-ca8b-5159f90af1a6@gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [xrwEPGC2IWJCRCryWCX8cIXJkfKPbESh]
x-ms-publictraffictype: Email
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: d34d770d-3a52-45c5-8645-08d7a38e5294
x-ms-traffictypediagnostic: DM6NAM12HT159:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 SPmH7AMefSQ9aBF0H6QvT8+6FMOogpOgHYaGkXs/7dFgO7TbKOWMStZjgNSHlfWC1OoA5nqdKBtcDHGoUuKifMRi456BSX4HJeOoNh8VWKzdQSXJv8Nt84a0XenpL/jZfQjkgoJ4eklfK1clHfp3MQT+PJRrhYPsNQ1iog0c+ZpUD6AuCkxBy1FrT0E4BIeH3a/uRczdGHhVWBEza84gI91TSse4gPSTGuOcbndiEGU=
x-ms-exchange-antispam-messagedata:
 Ack3q15wvu4L2bZvuleO4ybf07TXLdilP8ZOibTs/GENR/ygS96YUlWKTLfRIou99fDPgiyCluUWIl92AEgn9czNed4+Lk++PzOMTNX2BwsI9yw/y7WnKWTitfOyzILK3QdOEYQO4hmsvWqtm3tPYg==
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: d34d770d-3a52-45c5-8645-08d7a38e5294
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jan 2020 01:06:36.1283
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6NAM12HT159
Subject: Re: [PHP-DEV] [RFC] "use global functions/consts" statement
From: tysonandre775@hotmail.com (tyson andre)

> Imagine this scenario:=0A=
>=0A=
> * PHP 8 introduces the declare with only 'global' and 'default' options=
=0A=
> allowed, as proposed.=0A=
> * PHP 9 makes 'default' a synonym for 'global', because it's now the=0A=
> default, and adds a new 'fallback' option=0A=
> * I have an application that uses the fallback mode=0A=
> I can either:=0A=
>=0A=
> * Rewrite every file in my application prior to upgrading, and add a=0A=
> declare for 'global' mode to work in PHP 8, even though it will be=0A=
> redundant on PHP 9=0A=
> * Add a declare for 'fallback' mode, meaning my code works on PHP 9=0A=
without other changes, but can no longer compile on PHP 8=0A=
=0A=
I'd imagine that if there were significant changes,=0A=
they would go in the next major version,=0A=
and PHP 8.X.0 would (or wouldn't) add the new 'fallback' option and=0A=
possibly emit deprecation notices about the 'default' option or the absence=
 of an option.=0A=
(Possibly only if the file did have any ambiguous function/const references=
)=0A=
So done that way, you could run the same code both on the latest release of=
 PHP 8.x and PHP 9.0.=0A=
=0A=
I don't plan to change the default name resolution behavior in PHP 9, thoug=
h,=0A=
and if it does change, it might even be according to a different proposal,=
=0A=
so adding 'fallback' as a third option before we know what type of change i=
s planned=0A=
seems premature.=0A=
=0A=
I'd imagine the migration to 8.0 and 9.0 would be similar to 5.6 to 7.0:=0A=
https://www.php.net/supported-versions.php=0A=
- PHP 5.6 had an extended security support timeline,=0A=
  to give users time to update to php 5.6, validate and migrate to 7.0.=0A=
=0A=
  The timeline for the release prior to 8.0 would probably reflect how hard=
 it would be to migrate.=0A=
- Many things deprecated in PHP 5.x were removed in 7.0=0A=
=0A=
> Explicitly selecting a default for some value is useful when any value=0A=
> would actually be acceptable, and you want to delegate the choice of=0A=
> value to someone else. That's how PASSWORD_DEFAULT works, for instance -=
=0A=
> it means "please select a sane algorithm based on the current state of=0A=
> the world". I don't think that applies here - any file will have been=0A=
> written with one set of rules in mind, so "use whichever namespace rules=
=0A=
> are currently recommended" doesn't really make sense as an option IMO.=0A=
=0A=
'default' is more of a way to explicitly indicate you have made a decision =
on the option=0A=
for this file, and deliberately aren't using it for the file.=0A=
It's just a better name than the others I could possibly come up with ('unc=
hanged', 0, etc)=0A=
=0A=
I see `strict_types=3D0` as similar - The value `0` is currently rarely use=
d compared to leaving out the setting.=0A=
If php 8.x were to become stricter about type casting by default in a few w=
ays,=0A=
I doubt that there would be an argument for creating `strict_types=3D'php7'=
` before we knew what those changes are,=0A=
if there would be changes at all, and what the tradeoffs to supporting the =
php 7 semantics are.=0A=
`strict_types=3D0` would be used more often if the namespace-scoped declare=
() RFC was accepted.=0A=
=0A=
- Tyson=