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
signature.asc
Description: This is a digitally signed message part.
