Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69686 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61206 invoked from network); 18 Oct 2013 14:38:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Oct 2013 14:38:49 -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 74.125.82.46 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.46 mail-wg0-f46.google.com Received: from [74.125.82.46] ([74.125.82.46:58693] helo=mail-wg0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C5/87-23638-8F741625 for ; Fri, 18 Oct 2013 10:38:49 -0400 Received: by mail-wg0-f46.google.com with SMTP id m15so3790770wgh.13 for ; Fri, 18 Oct 2013 07:38:45 -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=Ajm39z5In9IFEMLl7Zp6zxTkf94P6psHnI+tdjVYD08=; b=lTtcLmu0tjjgNOL6hnKfqqhH71kvLHvbXkHhuIUUVaJMH44oC6Dl3hn5lrhJ8VozfE KSMFezc+g+FwnNAkUNb5VIk0ji7K91VNje2+hLW1YVg1qPuwfj2Giwr1t3z/mEaHneIb DwVk412gCRZaI0WBI3iiyoe+/SOH2IsmgM4e1fdr+MKrctr80esJjw3rJ3wz5cdffkuz 8fTsVny5cGvZfFR2GfYZIhU8PN4P85yVg121iKb04YN8SU+URsASJJVuuVaSE4Sd51D2 AAXnicJwGIhx9Kre27c6AScDY9maLrfQ4gBC2TYBhyidqLvFDPnhF9adrUsURZywc4xk Ak6A== X-Received: by 10.180.211.7 with SMTP id my7mr2742785wic.17.1382107125317; Fri, 18 Oct 2013 07:38:45 -0700 (PDT) Received: from [192.168.0.2] (cpc19-brig17-2-0-cust25.3-3.cable.virginmedia.com. [81.101.201.26]) by mx.google.com with ESMTPSA id s4sm27627330wiy.1.2013.10.18.07.38.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Oct 2013 07:38:44 -0700 (PDT) Message-ID: <526147EE.9080001@gmail.com> Date: Fri, 18 Oct 2013 15:38:38 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: PHP Internals References: <525C631E.1050008@gmail.com> <526136F8.6050300@rotorised.com> <52613DCD.2010301@gmail.com> <52613F62.6090407@rotorised.com> <52614225.1000800@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Proposal to deprecate create_function() From: rowan.collins@gmail.com (Rowan Collins) On 18/10/2013 15:16, Pierre Joye wrote: > On Fri, Oct 18, 2013 at 7:13 AM, Rowan Collins wrote: >> The absolute earliest this would actually be removed would be in 5.7, >> sometime in 2015. In fact, deprecating now but not expecting removal to be >> possible until 5.8 / 2016 seems reasonable to me. > I don't think we can ever remove it in 5.x. Is there a particular rule that separates the kind of BC breaks that are possible between 5.x releases vs those which would require bumping the major version? It is absolutely not the case that a program written for PHP 5.0 can be guaranteed to run under PHP 5.5 without modification. I thought PHP version numbers couldn't really be considered semantic like that, ever since PHP 6 was abandoned, and major language features from it were dropped into PHP 5.3 and 5.4. The current release policy could plausibly continue indefinitely, with a 5.13 in 2021; "never" is a long time... -- Rowan Collins [IMSoP]