Re: [RFC] Scope
| From: | Côme Chilliet | Date: | Tue, 10 Nov 2026 11:02:16 +0000 |
| Subject: | Re: [RFC] Scope | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-133050@lists.php.net to get a copy of this message | ||
Hello,
Le jeudi 29 octobre 2026, 13:22:04 heure normale d’Europe centrale Larry Garfield a écrit :
> Needing to write lots of boilerplate like that "just in case" is a red flag in my
> mind. Moreover, if the secondary vote doesn't pass initially but is introduced in some later
> version, it becomes a BC break for anything using a superglobal that happens to be called from
> within a scope, something the function (by design) doesn't know.
I had the same question reading the RFC, how can the future scope be implemented without BC break?
If suddenly scope starts to clear headers, ini_set or whatever, all existing code using it will
break?
Can you explain how future extension of what gets scoped can be achieved without BC break?
Côme
Attachment: [application/pgp-signature] This is a digitally signed message part. signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part. signature.asc