Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84387 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15753 invoked from network); 6 Mar 2015 20:10:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Mar 2015 20:10:33 -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.44 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.44 mail-qg0-f44.google.com Received: from [209.85.192.44] ([209.85.192.44:39845] helo=mail-qg0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AE/00-15314-8B90AF45 for ; Fri, 06 Mar 2015 15:10:32 -0500 Received: by qgdq107 with SMTP id q107so15391601qgd.6 for ; Fri, 06 Mar 2015 12:10:29 -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=zUsmzEoHzM8VwN4GXgZ7Cbd/nwBzKB2mM8Xg9TsADvE=; b=MS5XFtc5caE0J8i9mlNwcJOj0z/sYasg2HMsgTpr20PSh+Onmvqxu+xU8qbn6H/Z9F k6dcUWOH5QHG9pO6AhQOUwLGFlzcGVf9yYMXDyY75XiTajRRFfM/X2YFr629eD+y6dXm 7sqs3OBnlJOscTJyDcXjVPYPDaLLofm8Rm+rU88p2axyGASYAF5eWmatxNEEQ0HtEWcV AeDQL0rlR/s+ipmRyttOFZUS3amVNHeOaJ72eEHUUtGjH2SvI8Tkdn5sXnOLBElSZ6EH 8zPMOuEHbqo+5nusgMGz33nl8Z9sbFOIpfd+kSM6Jd6X5NACPFawNJanBJa+rK70+v6I /ACA== X-Received: by 10.140.238.79 with SMTP id j76mr22093351qhc.83.1425672628934; Fri, 06 Mar 2015 12:10:28 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.198.8 with HTTP; Fri, 6 Mar 2015 12:09:47 -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 05:09:47 +0900 X-Google-Sender-Auth: daDSpwUA9lHE0QIVYGexcSRY96M Message-ID: To: Arvids Godjuks Cc: Pierre Joye , Rowan Collins , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a1135cda29d1e2d0510a446a3 Subject: Re: [PHP-DEV] Consistent function names From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a1135cda29d1e2d0510a446a3 Content-Type: text/plain; charset=UTF-8 Hi Ardids, On Fri, Mar 6, 2015 at 8:22 AM, Arvids Godjuks wrote: > Why not take advantage of namespaces and do the new API, building it up > version by version (sure it can't be done in one go), so probably the > extensions gonna follow too. > That allows you to use as OO interface, so do the functions. Well, yes, it > will be under a namespace, but at least new projects can be started that > way. And old code will be easy enough to port, it's mostly a question of > refactoring tools. > This just does not work for people oppose to have new names for consistency. This proposal do not break scripts, almost. Therefore, namespace is not mandatory. We should have namespace for internal functions. I agree this part. Even if we have namespace that could work for internal functions, we still need standard confirming names. I propose PHP and IEEE as procedural function name standards. > > Aliasing is a stop-gap measure, isn't it? API's tend to get redesigned and > PHP's is due to a major makeover. So, why not embrace it? No one's forcing > to retire the old one any time soo, and I belive people understand it will > be a very long time before it is phased out, if ever (well, I think in like > 20 years probably is doable). And if done right, it may be done in a way > that if you don't need it, you can leave out the old API on compile stage - > not sure if doable thought. > It's not about gap or having new API, but having consistent name. Most procedural APIs except misordered parameter do not need new API. They only needs consistent names. Please suggest better/right way. Having namespace is not alternative for having consistent names. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a1135cda29d1e2d0510a446a3--