Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41304 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50356 invoked from network); 21 Oct 2008 08:07:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2008 08:07:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=kenashkov@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kenashkov@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.172 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: kenashkov@gmail.com X-Host-Fingerprint: 209.85.200.172 wf-out-1314.google.com Received: from [209.85.200.172] ([209.85.200.172:60426] helo=wf-out-1314.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DC/E0-44381-2DD8DF84 for ; Tue, 21 Oct 2008 04:07:47 -0400 Received: by wf-out-1314.google.com with SMTP id 26so2249828wfd.26 for ; Tue, 21 Oct 2008 01:07:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=YYtiW1v1rMmLf67K42jh7OUyi+SMUIkfYqThJeoFGaM=; b=qTl1JHBtdh9axLzyyduZcyIXCXVWSQ1XcxEM8pY36dh79VQVy0HSLABSml5mhldMcX K/731JhVhUnbefKf/NhXnrZZgUKaeU6K4Np1B2aCzzciiNgznAON6TtX0Kp6g7bp7aQG eXc7EGaov9ckCC+YHKGf3l5z7d7MNKc024cAM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=Sc8iArrf8Aofi6oSQ1/DbqbFPELX8DWfiNzD+cLVSw/Urf9h6Mi6GBrfdQyIAVikEO ROtqkrRw5GQc9yRWAg37mQl6WCAzboGebn9XUJdGz5LPhJYb6/oVwK8i4jJ+7swk/EgP vvY3CiNoKOSTZqRi/r8tBPucvnA9wNVPEHOY4= Received: by 10.142.70.11 with SMTP id s11mr3566950wfa.293.1224576463088; Tue, 21 Oct 2008 01:07:43 -0700 (PDT) Received: by 10.142.76.6 with HTTP; Tue, 21 Oct 2008 01:07:42 -0700 (PDT) Message-ID: <261daaa10810210107y623c0836nff5d463c84d7c14@mail.gmail.com> Date: Tue, 21 Oct 2008 11:07:42 +0300 To: internals@lists.php.net In-Reply-To: <646095388F084934B3647141FF1B459C@pc> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2143_15746043.1224576463051" References: <48F89F19.9040405@croscon.com> <3D.16.21706.F3CCCF84@pb1.pair.com> <015101c932e3$a37fb370$3ffc1f3e@foxbox> <200810202046.51235.et@php.net> <015c01c932e5$3671ff70$3ffc1f3e@foxbox> <8c35d7690810201245y29abc7ffo528fa3f9391fad01@mail.gmail.com> <48FCFA26.6010703@gmail.com> <022d01c932f6$202eee60$3ffc1f3e@foxbox> <646095388F084934B3647141FF1B459C@pc> Subject: Re: [PHP-DEV] Namespace issues From: kenashkov@gmail.com ("Vesselin Kenashkov") ------=_Part_2143_15746043.1224576463051 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline The N word discussion looks neverending... solution #3 from Gregory solves the ambiguity so I dont see how it will "create such nightmares in big projects with ambigous identifiers". I'm using the :: operator for the last 6 months and I had no such issues even without the fix (I'm not naming classes and namespaces in the same way, and I dont see why I would need to do so). Have you tried using it? If the __autoload performance problem is solved I dont see what is the problem with the current separator. I would wait for the opinion of Gregory and Stas Malyshev on this matter. On the other hand I dont think the backslash is ugly, and I think that the windows users will find it somewhat familiar for using it in tree structures like the namespaces. On Tue, Oct 21, 2008 at 10:33 AM, Stan Vassilev | FM wrote: > > Hi, > > Guys, this is like junior school in here. > > Let me put some things in perspective: > > 1) The location of backslash on foreign keyboard is entirely irrelevant for > the choice of namespace separator. Why? You already use this *every day* to > escape characters in your strings and regular expressions. Anyone complained > about the location of backslashes in there? No. > > 2) Where the backslash is, is also where the {} and [] are on those > kayboards, as some people already said. > > 3) "Backslash is ugly" <-- are you honest? Which is uglier: :::Foo() > ::Foo() or \Foo(); The last one at least has intuitive meaning (like file > paths: absolute path). Face it that you'll be typing either one of the above > three a *lot*, and pick one that makes sense visually and for newcomers > alike. I think that's the backslash. > > 4) "But we want the same operator". Well? I want a pony, the fact is > however, the other languages have the design to afford the same separator > for namespaces, static methods and members. Shoehorning this in PHP while > maintaing BC will create such nightmares in big projects with ambigous > identifiers, autoload performance issues, that you'd wish you go back and > change the damn namespace operator to just about *anything* but "::". > > I wish the people who have a clear opinion of the above voice their > opinion. For those who aren't quite sure what the issues in point 4 are, > please just stay low and follow the list until you do. > > Regards, > Stan Vassilev > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Vesselin Kenashkov developer at www.webstudiobulgaria.com ------=_Part_2143_15746043.1224576463051--