Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84194 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4232 invoked from network); 2 Mar 2015 22:09:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2015 22:09:48 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.42 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.42 mail-qg0-f42.google.com Received: from [209.85.192.42] ([209.85.192.42:38074] helo=mail-qg0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 70/40-14834-CAFD4F45 for ; Mon, 02 Mar 2015 17:09:48 -0500 Received: by mail-qg0-f42.google.com with SMTP id z60so9042022qgd.1 for ; Mon, 02 Mar 2015 14:09:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=tKNsvotEHLZraW69iixZj8Bx4oG+VLBUm0vxyYxgx+w=; b=bolAxN4KauRwC74YSof0/WS9kDA8WisnaLV+kc+ZmRxS0V8rppE2Hy96q7LjJ6QCiN 9WWDKuhBNItKI1C/m5MQNXeGDPnHw1adsQnMLA6wyotPMWb8nUPqIuuEIlt7zwY9vPzp xtmDto1I3luZzm3wODumY6S1IF44/jNPcKlkGFU5vkAZbPbNXg/3jM5ZllK1rcTvvqBG RaHV3At9XnnrWuXl9QIQG/JUXNiScqIfCWWu5gYZ7Z1M6cTToJZ0k88Dtv/8tU057IAB jnteYzdeFZLd/AeUbzVziU8mmhXWbsztqqN7rm6CeWtPxSlHfTx20KU8WUmNp8NfsBJT Jpxg== X-Received: by 10.140.29.74 with SMTP id a68mr26202329qga.106.1425334185312; Mon, 02 Mar 2015 14:09:45 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.198.8 with HTTP; Mon, 2 Mar 2015 14:09:04 -0800 (PST) In-Reply-To: <54F4DD6B.6090809@lsces.co.uk> References: <5E7DF0C5-BCB4-432A-A876-A5057FEBFBB5@gmail.com> <54F320E9.5000706@fischer.name> <54F4159A.6010903@fischer.name> <54F4DD6B.6090809@lsces.co.uk> Date: Tue, 3 Mar 2015 07:09:04 +0900 X-Google-Sender-Auth: sswLDfOEe2fue5u9_4_BNt9A07w Message-ID: To: Lester Caine Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a113a413ecd4a810510557979 Subject: Re: [PHP-DEV] Consistent function names From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a113a413ecd4a810510557979 Content-Type: text/plain; charset=UTF-8 Hi Lester, On Tue, Mar 3, 2015 at 7:00 AM, Lester Caine wrote: > On 02/03/15 21:39, Yasuo Ohgaki wrote: > > I wrote almost complete list. Please take a look at > > > https://wiki.php.net/rfc/consistent_function_names#list_of_functions_to_be_renamed > > While the idea of this is well meant, this is another major problem for > developers working with substantial legacy code yet needing to update > third party libraries. The statement "You can use old names for good." > is all very well, but if one library has been 'modernised and another > not, one has to work with both sets of names in parallel ... or maintain > legacy copies of the same libraries. > I think old function names should exist forever, so there wouldn't be issue you mentioned. > > Updating the PHP documentation is all very well, but how about > tutorials, books, third party tools and so on. I would still like some > help to update PHPEclipse to the recent PHP5 changes without having to > code a complete new set of reserved words and highlighting ... ore > reason to simply ditch PHP7 ... Old names works. No one forces users to use new names. I'll update PHP documents. It's a lot of work, but I'll. 3rd party documents may be update if they would like to. The issue here is PHP will keep inconsistent names forever or not. IMHO. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a113a413ecd4a810510557979--