Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84149 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42450 invoked from network); 2 Mar 2015 07:47:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2015 07:47:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=markus@fischer.name; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=markus@fischer.name; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fischer.name from 62.179.121.40 cause and error) X-PHP-List-Original-Sender: markus@fischer.name X-Host-Fingerprint: 62.179.121.40 fep20.mx.upcmail.net Solaris 10 (beta) Received: from [62.179.121.40] ([62.179.121.40:56345] helo=fep20.mx.upcmail.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 17/13-25952-F9514F45 for ; Mon, 02 Mar 2015 02:47:44 -0500 Received: from edge02.upcmail.net ([192.168.13.237]) by viefep20-int.chello.at (InterMail vM.8.01.05.13 201-2260-151-135-20130320) with ESMTP id <20150302074740.RCAU6348.viefep20-int.chello.at@edge02.upcmail.net> for ; Mon, 2 Mar 2015 08:47:40 +0100 Received: from mail02.home ([213.47.1.174]) by edge02.upcmail.net with edge id yXng1p00R3lFLNl01XngBd; Mon, 02 Mar 2015 08:47:40 +0100 X-SourceIP: 213.47.1.174 Received: from mail02.home ([192.168.1.14] helo=lv426.local) by mail02.home with esmtp (Exim 4.72) (envelope-from ) id 1YSL4l-0007qh-HG for internals@lists.php.net; Mon, 02 Mar 2015 08:47:40 +0100 Message-ID: <54F4159A.6010903@fischer.name> Date: Mon, 02 Mar 2015 08:47:38 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <5E7DF0C5-BCB4-432A-A876-A5057FEBFBB5@gmail.com> <54F320E9.5000706@fischer.name> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-Spam_report: Spam detection software, running on the system "scanner01.home", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hello! On 01.03.15 21:19, Yasuo Ohgaki wrote: >>> The answer is no, it's just not worth it. Having a function called >> str_pos which is an alias of strpos, but only on some versions, is more >> confusing, not less. >> >> My sentiment too. Factor in that someone already using the proposed >> himself, things can only go south from here. >> >> If PHP wants to clean up, then do it right: use a namespace for it. > > > I agree use of namespace is better solution. It's rather severe BC, though. > How about rename functions except "string" and "array" related functions? > > BTW, I cannot change document system, but I'm going to update all doc > contents if this passes. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Subject: Re: [PHP-DEV] Consistent function names From: markus@fischer.name (Markus Fischer) Hello! On 01.03.15 21:19, Yasuo Ohgaki wrote: >>> The answer is no, it's just not worth it. Having a function called >> str_pos which is an alias of strpos, but only on some versions, is more >> confusing, not less. >> >> My sentiment too. Factor in that someone already using the proposed >> himself, things can only go south from here. >> >> If PHP wants to clean up, then do it right: use a namespace for it. > > > I agree use of namespace is better solution. It's rather severe BC, though. > How about rename functions except "string" and "array" related functions? > > BTW, I cannot change document system, but I'm going to update all doc > contents if this passes. I'm not sure we're on the same page. I'm talking about moving in "no-BC-break" way, if at all. That is, no existing function be touched. As to whether namespaces-aliases are really necessary I leave for others. I think a sensible thing to do at this stage would be, rather than changing existing stuff, laying the ground work how to do it in the future. What I mean is: an RFC for consistent introducing new "names" in the PHP language. So that /future/ functionality does not always get slapped into the global namespace but that we finally start using our reserved PHP\ namespace and put stuff in there instead of the global pollution. Yeah, I think that direction is a sensible start and gather peoples mindset about this instead of going backwards, renaming stuff without clear plan, etc. thank you, - Markus