Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:1655 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21209 invoked from network); 18 May 2003 12:39:55 -0000 Received: from unknown (HELO ied.ac.cn) (211.99.43.218) by pb1.pair.com with SMTP; 18 May 2003 12:39:55 -0000 Received: (qmail 13722 invoked by uid 610); 18 May 2003 20:07:29 +0800 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 May 2003 20:07:29 +0800 Date: Sun, 18 May 2003 20:07:29 +0800 (CST) X-X-Sender: hewei@web.ied.ac.cn To: internals@lists.php.net Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Case insensitivity weakened the power of overloading From: hewei@ied.org.cn (Wei He) Hi, Besides in-php use of class method/property overloading, XML-RCP can be a perfect application of this functionality. But again it touchs the sensitive topic of case sensitivity of Zend. With CS, an RPC call will be $rpcclient->methodname($arg1, $arg2); instead of $rpcclient->call($methodname, $arg1, $arg2); SOAP'w workaround of collecting all available methods is efficient and sometime not support by all XML-RPC servers. Especially when the method is also a dynamic call on the server side. Think of a Python(Zope) XML-RPC server. As Zend Engine 2 can change the world such a lot, why not just a little bit on class/method/function name's case sensitivity? When I am wriing this message, I'm compiling my PHP with CS patch. I noticed, besides some internal places like Zend, aggregate and overload need to be patched, the bundled PEAR also need to be patch to at least make the RPM buildable. I also saw how the author hates case insensitivities, so I'm not afraid of posting this issue again. Please give me some reasons why not. How about in Zend Engine 2? Wei He