Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:32813 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49280 invoked by uid 1010); 16 Oct 2007 12:33:35 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 49264 invoked from network); 16 Oct 2007 12:33:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Oct 2007 12:33:35 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 85.10.196.195 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 85.10.196.195 serveforce1.backendmedia.com Linux 2.6 Received: from [85.10.196.195] ([85.10.196.195:44612] helo=serveforce1.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 08/92-30952-C9FA4174 for ; Tue, 16 Oct 2007 08:33:32 -0400 Received: from [192.168.10.195] (164.31.3.213.fix.bluewin.ch [213.3.31.164]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by serveforce1.backendmedia.com (Postfix) with ESMTP id 233501224A91; Tue, 16 Oct 2007 14:36:51 +0200 (CEST) In-Reply-To: <7C37FF3A0196094F95430BA95952032201611D@s1.mkj.lan> References: <7C37FF3A0196094F95430BA95952032211B7C5@s1.mkj.lan> <7C37FF3A0196094F95430BA95952032211B7C7@s1.mkj.lan> <72129346.20071014092922@marcus-boerger.de> <7C37FF3A0196094F95430BA95952032211B7CC@s1.mkj.lan> <19939840.20071014231353@marcus-boerger.de> <002f01c80f5b$d645d340$15b2a8c0@unterwegs> <7C37FF3A0196094F95430BA95952032211B7D2@s1.mkj.lan> <4714881F.1030302@cschneid.com> <7C37FF3A0196094F95430BA95952032201611B@s1.mkj.lan> <47149337.9000209@cschneid.com> <7C37FF3A0196094F95430BA95952032201611D@s1.mkj.lan> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: Cc: "Christian Schneider" , Content-Transfer-Encoding: 7bit Date: Tue, 16 Oct 2007 14:33:09 +0200 To: Hans Moog X-Mailer: Apple Mail (2.752.3) X-backendmedia-com-MailScanner-Information: Please contact the ISP for more information X-backendmedia-com-MailScanner: Found to be clean X-backendmedia-com-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=0.075, required 6, AWL -0.03, RDNS_DYNAMIC 0.10) X-backendmedia-com-MailScanner-From: mls@pooteeweet.org X-Spam-Status: No Subject: Re: AW: AW: AW: [PHP-DEV] Method overloading by method signature From: mls@pooteeweet.org (Lukas Kahwe Smith) On 16.10.2007, at 13:43, Hans Moog wrote: > > I agree. But PHP (until PHP 5.2.x) was the wrong language for > everyone who wanted to use namespaces, too. > But a programming language is able to evolve and sometimes new > features are really usefull and should be included. And in this > special case the new feature would not harm anyone because it would > be fully backward compatible and in my humble opinion it would push > php to an enterprise level when it comes to object orientation. The point is that I do not see this feature at all relevant to solving the web problem. This is where PHP needs to focus. Namespaces help in solving the web problem, because it eases cooperation of independent developers to supply libraries. The feature you are proposing is solved easily in userland (just like named parameters). Its is a feature I could see using in a heavy lifting language, but not in a glue language. Where do we draw the line? Somewhere relatively arbitrary, but my gut tells me that this is a good candidate to be on "lets leave it out of php" side of the line. regards, Lukas