Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70655 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45770 invoked from network); 16 Dec 2013 09:44:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2013 09:44:29 -0000 Authentication-Results: pb1.pair.com header.from=robert@cerny-online.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=robert@cerny-online.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain cerny-online.com from 83.220.144.26 cause and error) X-PHP-List-Original-Sender: robert@cerny-online.com X-Host-Fingerprint: 83.220.144.26 webbox122.server-home.org Linux 2.6 Received: from [83.220.144.26] ([83.220.144.26:40625] helo=webbox122.server-home.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A5/82-32483-C7BCEA25 for ; Mon, 16 Dec 2013 04:44:28 -0500 SMTP-policy: ok Received: from [192.168.1.50] (232.235-245-81.adsl-dyn.isp.belgacom.be [81.245.235.232]) by webbox122.server-home.org (Postfix) with ESMTPA id F1CB1C069B for ; Mon, 16 Dec 2013 10:48:43 +0100 (CET) Message-ID: <52AECB78.8020705@cerny-online.com> Date: Mon, 16 Dec 2013 10:44:24 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: internals@lists.php.net References: <52ABFE84.8010404@cerny-online.com> <52AE93E9.7070903@cerny-online.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Flexible function naming From: robert@cerny-online.com (Robert Cerny) Tjerk Meesters wrote: >>>> This small change would allow coding teams to create a consistent code >>> base based on 'their' guidelines. Motto: "Have it your way!". >>> >>> No. >>> >>> What is wrong with having a consistent code base all the way, also >> covering legacy code? I consider this a pretty neat language feature. > Consistency doesn't stop at how functions are named; there are enough > functions that have an unintuitive order of function parameters, this isn't > addressed in your proposal. You are right. There is more reasons for the inconsistent appearance of a large PHP code base. The one that you mentioned is IMHO a major annoyance while authoring code, it is only minor when reading code, in particular if you keep the numbers of function arguments small. > If it were just the naming you wish to address, I would suggest writing an > extension first and see how that catches on. Thanks, that is helpful. I look into that! Robert