Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84330 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7263 invoked from network); 5 Mar 2015 09:40:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Mar 2015 09:40:30 -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.53 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.53 mail-wg0-f53.google.com Received: from [74.125.82.53] ([74.125.82.53:35362] helo=mail-wg0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CE/E0-01843-D8428F45 for ; Thu, 05 Mar 2015 04:40:30 -0500 Received: by wggz12 with SMTP id z12so52273874wgg.2 for ; Thu, 05 Mar 2015 01:40:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type:subject:from:date:to:cc :message-id; bh=W5SHgdJudAs2U8fM/lyOFSVsT6/r3F43/4KQYLut274=; b=hR8bU2F3p3u8+E1jIKDQra/sTUe8EgZD9Cq30ydVkC4m1b8Oal4GIQBbzqSQeXNb4Y vKX57wFmUDN7eSsM2XPibSxzVmlumPDRCYaDqlajTP/oWwrXvQ5S/38qEM9z37IsEwED QMDED/DUft54SiSpvV4JI9ETbTpp3rgsGfvkV54jqrqL9fba7l5a5tD1uw9SzVqeA8fN /hNaISMgtp8/EHOFyImqv88Z2uU4IZWITTyFr+fWOrIpPRRr98lsUEwSGhazFRB7xylU qPfTDT+h2G9vCLd/KHeNAWccLcRLi+ZVA8hVYOoeyNeZYDNN9U+59kcDZ8nUD7NMEgSu pI7Q== X-Received: by 10.194.60.19 with SMTP id d19mr16591434wjr.133.1425548425127; Thu, 05 Mar 2015 01:40:25 -0800 (PST) Received: from [192.168.0.122] ([62.189.198.114]) by mx.google.com with ESMTPSA id gm2sm10817133wib.5.2015.03.05.01.40.22 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Mar 2015 01:40:23 -0800 (PST) User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Date: Thu, 05 Mar 2015 09:40:07 +0000 To: Yasuo Ohgaki CC: "internals@lists.php.net" Message-ID: <726CA870-917C-4270-A129-AFE106E0A380@gmail.com> Subject: Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names From: rowan.collins@gmail.com (Rowan Collins) On 5 March 2015 08:50:12 GMT, Yasuo Ohgaki wrote: >Hi Niklas, > >On Thu, Mar 5, 2015 at 5:29 PM, Niklas Keller wrote: > >> If we introduce those new aliases, it should be clearly stated in the >docs >> which function should be used, maybe we can remove the old one in the >far >> future then. But the more important point is, that it's not that >confusing >> to users. Which one should I use? Why's there another one? We already >have >> that situation with `count` and `sizeof`. > > >Good point! >I'll update documents so that main function is prefered name/function >to be >used. This would be fine if all the users read the manual, and only the manual. What about the thousands of books, tutorials, blog posts, Stack Overflow q&as, etc, all mentioning the names and behaviour that have been around for 15 to 20 years? Not to mention the thousands of lines of existing code which people will not only need to read and understand, but also contribute to without accidentally breaking compatibility with old versions of PHP. Regards, -- Rowan Collins [IMSoP]