Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70966 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65253 invoked from network); 2 Jan 2014 19:42:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Jan 2014 19:42:56 -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.215.53 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.53 mail-la0-f53.google.com Received: from [209.85.215.53] ([209.85.215.53:43512] helo=mail-la0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DF/23-48256-F31C5C25 for ; Thu, 02 Jan 2014 14:42:56 -0500 Received: by mail-la0-f53.google.com with SMTP id mc6so7517744lab.40 for ; Thu, 02 Jan 2014 11:42:53 -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=DzPcAxHPaf8QT1UIXlB6JRqc9AYx48noReBOcwMKJ2o=; b=CJmI+c7O5xWtIsu+bNuoSQ6kRkwZeR7jLq/qOTbhlNm24SDBGk0MsA30vGHKJ90RcS RnXpd/EcOouLLrAnwn+L44+UXpVaEOLSBd7NtCvfLsCgJHhwcQRiXRU9bijO0KJToHfJ JNdUfWm2cEAtNfOTYa73oPo/Ungr47f0Z6j+ciHEsqIUGvWhDJanlE/SZFZanUVUG7Gq 25Sdi8FtCjH4tvhuGsI+Jeq/2JdsipFoJAKpat/lFaJ4GnOo1h+Iiy9X4kUOxsCZvya7 +3vNkV/5kSdD5V0DyHuJwjWN69tw5R4c+RQD1x38A122I6pQzMpN39B9AiRcYAYn/Iwu MJwQ== X-Received: by 10.112.172.69 with SMTP id ba5mr3315087lbc.55.1388691773141; Thu, 02 Jan 2014 11:42:53 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.6.68 with HTTP; Thu, 2 Jan 2014 11:42:12 -0800 (PST) In-Reply-To: <0bae3e8fb5acff88a1aba0bea6bd264d@yamiko.org> References: <52BE8F35.9090104@b1-systems.de> <52C4A415.3040101@gmail.com> <52C4ADC8.1090009@lerdorf.com> <52C510CF.3030604@garfieldtech.com> <0bae3e8fb5acff88a1aba0bea6bd264d@yamiko.org> Date: Fri, 3 Jan 2014 04:42:12 +0900 X-Google-Sender-Auth: KhtK34k69u3dCw82RMBxz38HsdM Message-ID: To: Robert Parker Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c23404d737e904ef01ffcc Subject: Re: [PHP-DEV] [PHP6] Function name consistency From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c23404d737e904ef01ffcc Content-Type: text/plain; charset=UTF-8 HI all, On Fri, Jan 3, 2014 at 2:49 AM, Robert Parker wrote: > I would consider myself one of those php developers. I know very little c, > and java. Javascript is my second language after php. Most php developers > have yet to move towards 5.3 and don't know how to even use namespaces or > what they are. They often use wordpress or drupal which are very slow to > adapt. > > Considering how slow and hard it is for most php developers to migrate to > new versions of php I do not think creating aliases or changing the names > would be beneficial. Different developers would use different aliases and > it would confuse a lot of php developers. > This proposal does not intend to force users to adopt new names, but ensure PHP popularity in the long run. Are new users willing to learn language that have full of inconsistent names even for basic/standard/default functions? My intention to have consistent function names for old function is - to ensure PHP as attractive language to learn even 10 or 20 years later. I agree that adoption of new feature is slow. If we made function names consistent now, there would be codes around uses historic names 10 years later, but it does not matter for the purpose of this proposal. De facto Standard names such as strchr() would be acceptable names even 20 years from now. Other functions such as GD functions are better to have consistent names. Please consider this proposal is for new users that will learn PHP from now or in the future. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c23404d737e904ef01ffcc--