Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85512 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 649 invoked from network); 27 Mar 2015 18:13:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Mar 2015 18:13:42 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.174 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.212.174 mail-wi0-f174.google.com Received: from [209.85.212.174] ([209.85.212.174:38815] helo=mail-wi0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A4/49-38005-5DD95155 for ; Fri, 27 Mar 2015 13:13:42 -0500 Received: by wibgn9 with SMTP id gn9so42047668wib.1 for ; Fri, 27 Mar 2015 11:13:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=EwV8RPi1jg/y5qFl8jbtNaDhft7VrQ1Qlf1+XcapO3Q=; b=YsHe440F3BvqL4943JX8dUcqhdErmFctvdK2MNYzyqPkBX6I3funtrkgGeMD4QRTfl gmunInx+JxwnqlSQlvk12021qjJpLD6zKIdR1YXkXcoGwQv6DoOL85KhtLvDP+1bgNKl VyHGXAAbhv7AWWq6qFf/n4azkjmmXRITaGeB/JqUE4/S3wa4UbOdTF0boDoW/BMjJCgN Mr1LwbUn9rcpPci8RAkqOKEzi6f6HncivLxLZxlk8V9XWeMgNlgkDjIS8oS/teNJlET8 hZFnpDK/QGaDSdX2LehYeap/g5RbBbyBYeCA0DjZ2Z8s4mbRU5dc6IdL0UN2Xi+sFCqI FaFA== X-Received: by 10.194.78.114 with SMTP id a18mr40979177wjx.0.1427480018672; Fri, 27 Mar 2015 11:13:38 -0700 (PDT) Received: from [192.168.0.159] ([62.189.198.114]) by mx.google.com with ESMTPSA id kr5sm3900742wjc.1.2015.03.27.11.13.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Mar 2015 11:13:37 -0700 (PDT) Message-ID: <55159D9D.4040001@gmail.com> Date: Fri, 27 Mar 2015 18:12:45 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: internals@lists.php.net References: <547CEB74.9070807@ralphschindler.com> <54D1BF4B.30008@gmail.com> <55158859.5000606@ralphschindler.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] $http_response_header From: rowan.collins@gmail.com (Rowan Collins) Ferenc Kovacs wrote on 27/03/2015 16:50: > yeah, but we already mentioned/discussed this that the removal would > require introducing another way (eg. adding a method) for fetching the > headers. > I think that introducing this method can happen in a minor version(without > removing the $http_response_header variable), so I will create a pull > request and ask Julien about including it in 5.5 and upwards. I've seen comments to this effect before, and don't really understand the motivation for adding functions in patch versions. Personally, I'd never rely on such a function, because it would mean my code relied on a version spec like "(>= 5.5.23 && < 5.6.0) || >= 5.6.7", which is just horrible. And on the negative side, there's the (admittedly very small) possibility of unexpectedly colliding with someone's existing function. The definition at SemVer.org (I know PHP doesn't officially follow this definition, but it's a well-thought out point of reference) makes clear: > Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. Isn't it enough if the new function, and the deprecation of the variable, is snuck into 7.0, or added in 7.1? Regards, -- Rowan Collins [IMSoP]