Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60244 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30013 invoked from network); 20 Apr 2012 18:49:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Apr 2012 18:49:35 -0000 Authentication-Results: pb1.pair.com smtp.mail=php-php-dev@m.gmane.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=can5koy@gmail.com; sender-id=unknown Received-SPF: pass (pb1.pair.com: domain m.gmane.org designates 80.91.229.3 as permitted sender) X-PHP-List-Original-Sender: php-php-dev@m.gmane.org X-Host-Fingerprint: 80.91.229.3 plane.gmane.org Received: from [80.91.229.3] ([80.91.229.3:42742] helo=plane.gmane.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A7/CA-63732-EBFA19F4 for ; Fri, 20 Apr 2012 14:49:34 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SLItd-0008HJ-0N for internals@lists.php.net; Fri, 20 Apr 2012 20:49:29 +0200 Received: from 46.197.249.211 ([46.197.249.211]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Apr 2012 20:49:28 +0200 Received: from can5koy by 46.197.249.211 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Apr 2012 20:49:28 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: internals@lists.php.net Date: Fri, 20 Apr 2012 21:48:36 +0300 Lines: 24 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: 46.197.249.211 User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:11.0) Gecko/20120312 Thunderbird/11.0 In-Reply-To: Subject: Re: [PHP-DEV] Complete case-sensitivity in PHP From: can5koy@gmail.com ("C.Koy") On 4/20/2012 8:57 PM, Kris Craig wrote: > > Turkish localization notwithstanding (I confess that I know absolutely * > nothing* about that lol), one possible use-case could be if you're > including an external library/framework that contains a function with the > same name but different case. I'm not sure how likely that is, mind you, > but I can see that as one potential benefit. Either way, I guess my point > is that the arguments for/against this seem to parallel the arguments for > Windows-style fso case-insensitivity vs. Unix-style fso case-sensitivity. > Java, C#, Python, Ruby... are all case-sensitive. This is not a feature to be (mis-)used so that one can have a function named myfunc() and MyFunc() in the same code base. Case-insensitive class/function/interface names is a confusion for everyone with non-PHP development experience. There's not a modern OO platform that defines an interface named 'IDispatch' and later allows it to be referenced as 'idispatch' or 'iDispatch'. And PHP is becoming more OO with every major release. Overall, full case-sensitivity seems to be a natural step in PHP's evolution.