Re: [RFC] Add Directive to M ake All Namespaced Function CallsGlobal
| From: | Rowan Tommins [IMSoP] | Date: | Mon, 05 Aug 2024 21:20:59 +0000 |
| Subject: | Re: [RFC] Add Directive to M ake All Namespaced Function CallsGlobal | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-124789@lists.php.net to get a copy of this message | ||
On 4 August 2024 13:08:22 BST, "Christoph M. Becker" <cmbecker69@gmx.de> wrote:
>On 04.08.2024 at 13:42, Nick Lockheart wrote:
>
>> To that end, I have created the following RFC:
>>
>> https://wiki.php.net/rfc/global_function_parser_directive
>> I am asking that we discuss and vote on the following question:
>
>Please open a new thread about your RFC (i.e. don't reply to some other
>message, but rather send a new message to the mailing list). Otherwise
>it might easily be overlooked. See also
><https://wiki.php.net/rfc/howto>.
Please can people stop replying on this sub-thread until a proper new thread is created.
I know GMail and some other mail clients have a heuristic definition of "conversation",
but many clients and archives - including the widely used externals.io - are based on the
standardised Reply-To and Thread-Id headers, which are not reset based on a new subject line.
In those UIs, this is still part of the completely unrelated deprecation voting thread <https://externals.io/message/124506>, which was
already becoming unmanageably long due to the protracted debate about hashing functions.
Regards,
Rowan Tommins
[IMSoP]