Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41492 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65068 invoked from network); 27 Oct 2008 23:28:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Oct 2008 23:28:18 -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 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:49215] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A0/46-34199-19E46094 for ; Mon, 27 Oct 2008 18:28:18 -0500 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id 8D7334144059; Mon, 27 Oct 2008 22:33:57 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3WsZGZJgaxCi; Mon, 27 Oct 2008 23:33:56 +0100 (CET) Received: from [192.168.0.151] (77-58-151-147.dclient.hispeed.ch [77.58.151.147]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by bigtime.backendmedia.com (Postfix) with ESMTP id 76F67414400F; Mon, 27 Oct 2008 23:33:56 +0100 (CET) Cc: Sean Coates , Josh Davis , Rodrigo Saboya , internals@lists.php.net Message-ID: <15F5A0BE-B92B-4C8B-AD7B-62DAFE4C80FF@pooteeweet.org> To: Stanislav Malyshev In-Reply-To: <4906405F.7090205@zend.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 27 Oct 2008 23:32:51 +0100 References: <49048EC1.9060908@chiaraquartet.net> <4905EDA9.9050301@zend.com> <11c607a60810271049y419c252q7e21cde9221f1996@mail.gmail.com> <490600CD.5020207@zend.com> <11c607a60810271252r4bedeea8q59ce5423891d8e59@mail.gmail.com> <49061E01.8060503@zend.com> <11c607a60810271344i1a8cf53fl149447ad2f687f99@mail.gmail.com> <490628DB.9060209@zend.com> <11c607a60810271422l68949427pe31786275b0b152c@mail.gmail.com> <08747094-6B50-4A0D-9057-DFD12108B6C6@caedmon.net> <94CCB864-179A-48DA-A89A-3859796A9257@pooteeweet.org> <49063A1D.7070804@zend.com> <4906405F.7090205@zend.com> X-Mailer: Apple Mail (2.929.2) Subject: Re: [PHP-DEV] namespace separator and whining From: mls@pooteeweet.org (Lukas Kahwe Smith) On 27.10.2008, at 23:27, Stanislav Malyshev wrote: >> this is how PHP got its huge userbase. we let people grow with >> their needs. > > And how exactly it serves the needs of people by secretly making > their applications orders of magnitude slower, and then saying "oh, > that's because you failed to read paragraph 16.4.5.1 in the manual, > you should really read that paragraph before pretending to be PHP > programmer!". Good environment or does what you want it to do, or > fails, explaining to you why it doesn't work - it doesn't do it half > way half broken and then blames you for not reading some obscure > note in the manual. That's not how I see helping. ok this might be a shock for you .. but the vast majority of our user base does not have a performance problem (thats not to say we need to waste their CPU cycles .. we all love the planet). then as we are suggesting they will not have to read a manual. in our proposal they can use all the existing books, examples on PHP, migrate their code easily to namespaces and things will just work. if they advance beyond the point of absolute n00b, they will learn to look for E_NOTICE and by that time they will know how to fix their performance issues (if they have any) without having to open a manual. in your scenario, all examples in the world will mysteriously break when they are used inside a namespace (which they might have gotten from another example or some inherited code). regards, Lukas Kahwe Smith mls@pooteeweet.org