Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106171
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
In-Reply-To: <CAJW__o0GLjcagzF0ZpEK54yyhkFpgV6tm4p+ihnZvv-dC3YFUQ@mail.gmail.com>
Date: Mon, 8 Jul 2019 15:41:05 +0200
Cc: Internals <internals@lists.php.net>,
 Nikita Popov <nikita.ppv@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-ID: <32BFA854-5FDB-4F56-941C-3B9F23D6D2E3@gmail.com>
References: <CAJW__o0GLjcagzF0ZpEK54yyhkFpgV6tm4p+ihnZvv-dC3YFUQ@mail.gmail.com>
To: Kalle Sommer Nielsen <kalle@php.net>
Subject: Re: [PHP-DEV] [RFC] Deprecations for 7.4
From: claude.pache@gmail.com (Claude Pache)

The deprecation RFC lists `apache_request_headers()`, because it is =
=E2=80=9Can Apache-specific name is also available in other SAPIs, even =
though it is also available under the SAPI-independent name =
getallheaders()=E2=80=9D.

Have you ever thought about making a more thorough and consistent change =
with other similar functions, instead of just picking one particular =
function because it is the only one in its category that has a =
documented alias? In five minutes, I=E2=80=99m thinking of the following =
obvious things:

* using a less ambiguous name than `getallheaders()`, given the =
existence of both `apache_request_headers()` and =
`apache_response_headers()`;

* renaming all `apache_*()` functions that are available in other SAPI =
into a SAPI-independent name;

* treating all `nsapi_*()` functions as well.

=E2=80=94Claude