Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84393 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48602 invoked from network); 7 Mar 2015 01:40:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Mar 2015 01:40:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.175 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.214.175 mail-ob0-f175.google.com Received: from [209.85.214.175] ([209.85.214.175:35089] helo=mail-ob0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 23/80-39204-EF65AF45 for ; Fri, 06 Mar 2015 20:40:15 -0500 Received: by obbgq1 with SMTP id gq1so24196918obb.2 for ; Fri, 06 Mar 2015 17:40:12 -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=y2OIl7LxdaRb5Vp1Sa5vuQH+wK2jKbINP7qKqsDHXbk=; b=0FBstWTd2ZpMH6hjYBiHDeF66gzqeIkzD82ClupByrgyN8uBskzKlOCv3+/PnlSy3o cmXH1CsFt5HYxdyb2umks5YQyidwXXsHxUCViX/skBRNo32OaOE1qDYvcBEtaS+bjmgY o48KG2r5VVuAtuoDjejY36Js8zFij57XcR6/9w1/us33Q/tE41+EfueTrvkQILhfKQM0 jDuqbYSYPENHSHInx+iUvH9MJttnzcP7VwQVkwg9F9ysV/HDBw8hckog0e+0zbL2nUEc rIzED716mv9s8+PtLKabpe/+1NcYOF5QgtjHLk6xnW+gJ69ATidMuw4UhwgKRB+jboYL 4TpQ== X-Received: by 10.202.58.8 with SMTP id h8mr12542392oia.93.1425692412079; Fri, 06 Mar 2015 17:40:12 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.202.58.2 with HTTP; Fri, 6 Mar 2015 17:39:31 -0800 (PST) In-Reply-To: References: <54F4E93C.80206@gmail.com> <54F4EBEC.2090702@garfieldtech.com> <54F4F3FC.6060501@fischer.name> <54F4FDFB.8010701@lsces.co.uk> <54F5895D.3090002@gmail.com> <554F0C3F-770F-4694-A5AB-FDC54FCCBF00@gmail.com> <1FCB68B8-3E55-4B5D-B805-9D92D848A3A1@gmail.com> <5D8591E2-5AE6-4B4C-AAE0-3D15523410AC@gmail.com> <54F83C4D.1020206@gmail.com> Date: Sat, 7 Mar 2015 10:39:31 +0900 X-Google-Sender-Auth: Z8UKWZKSp8eMUPeAlMcMrgvMFFg Message-ID: To: Pierre Joye Cc: Arvids Godjuks , Rowan Collins , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a113cd866c7f50e0510a8e174 Subject: Re: [PHP-DEV] Consistent function names From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a113cd866c7f50e0510a8e174 Content-Type: text/plain; charset=UTF-8 Hi Pierre, On Sat, Mar 7, 2015 at 7:18 AM, Pierre Joye wrote: > > Please suggest better/right way. Having namespace is not alternative for > > having consistent names. > > I think I did, and many other. But you seem to be convinced that > consistency in names is the top priority and will suddenly make these > APIs easier to use. I think we should agree to disagree and move to > vote. I do not see any value in this discussion since quite some time, > it is hair splitting solutions for naming, namespace, etc while not > having an agreement on how and where to do it, except the std C names. I agree namespace can be used to fix naming/parameter issues with zero BC. What I'm saying here is We need new name function (and documentations/codes update) anyway We may provide new names and new parameter order in new namespace. The difference is "alias" or "namespace" basically. I don't object to use namespace for it at all. In fact, I would love to have it even if there is issue like writing extremely difficult to read code is possible. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a113cd866c7f50e0510a8e174--