Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41658 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71679 invoked from network); 4 Nov 2008 18:05:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Nov 2008 18:05:57 -0000 X-Host-Fingerprint: 201.17.97.233 unknown Received: from [201.17.97.233] ([201.17.97.233:1588] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B1/3C-15458-30F80194 for ; Tue, 04 Nov 2008 13:05:56 -0500 Message-ID: To: internals@lists.php.net Date: Tue, 04 Nov 2008 16:05:52 -0200 User-Agent: Thunderbird 2.0.0.17 (X11/20080914) MIME-Version: 1.0 References: <49048EC1.9060908@chiaraquartet.net> <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> <490747B2.2010201@zend.com> <4D9A8597-EFE6-418A-B7F6-EAD9ED2361A5@pooteeweet.org> <7FA6946B-57B9-4BC0-B2F1-AFD47572F363@pooteeweet.org> <491071EC.7020501@cschneid.com> <49107527.7060604@chiaraquartet.net> <02e001c93e9c$a8874f30$3ffc1f3e@foxbox> <1219068137.20081104174457@marcus-boerger.de> <02e901c93e9d$389a8c90$3ffc1f3e@foxbox> <1225818078.9595.1.camel@goldfinger.johannes.nop> <032001c93ea0$118e2eb0$3ffc1f3e@foxbox> In-Reply-To: <032001c93ea0$118e2eb0$3ffc1f3e@foxbox> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 201.17.97.233 Subject: Re: [PHP-DEV] namespace separator and whining From: rodrigo.saboya@bolsademulher.com (Rodrigo Saboya) Steph Fox wrote: >> IT will break the code from everybody who doesn'T expect such a flag >> exists and the average application user won't know and jsut see errors >> which "randomly" occur. > > Erm, how is that going to happen? > > This is basically a tighter setting that can *optionally* be used and > should *always* be used in development. It would be documented loud and > clear in the PHP manual, where people go to find out about > new/different-from-Java language elements. There's a *possible* slowdown > and *possible* conflicts if you never use it, but the people most likely > to never use it are those least likely to be loading lots of third-party > OO code in the first place. > >> No ini settings for basic behavior. > > Ah well we might as well throw out E_STRICT too! > > - Steph > I don't think it's going to prevent writing portable code, at least for serious framework developers, because they'll prefix their classes anyway. But I think it's dangerous and will cause unexpected behavior for the average user. This was discussed before, I'm with Stas: Global classes cannot be overriden unless explicitly prefixed. -- Rodrigo Saboya