Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41430 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33167 invoked from network); 27 Oct 2008 09:33:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Oct 2008 09:33:18 -0000 Authentication-Results: pb1.pair.com header.from=tudor.prodan@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=tudor.prodan@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.158 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tudor.prodan@gmail.com X-Host-Fingerprint: 72.14.220.158 fg-out-1718.google.com Received: from [72.14.220.158] ([72.14.220.158:52098] helo=fg-out-1718.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5C/68-34199-CDA85094 for ; Mon, 27 Oct 2008 04:33:16 -0500 Received: by fg-out-1718.google.com with SMTP id 16so2145011fgg.23 for ; Mon, 27 Oct 2008 02:33:13 -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:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=M6CZYRbNLTf1vKVxnKfX5L7SvkYD8IxRLg06rY2ipFE=; b=Ob2u8l6vJp93yQ9KZWVh0PiGJ/xlnn8EJH/Is3ucYQCbr+iJLD5YlZtjBBqvCAuoF4 MbpT+rUbCcjRIKW41whk9FnH1ttvPpYUBlGGHw1957pRpvn55xkE2nzk+bd4MoBGuzwj 8SNgsoQjYiyQ1oB8Q6/GrwA+SoIljHuwvdq+I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=XlFLanIraYVEu6mXbGzS2cfjzXkEUHzjbnYlP1uqe54xgIy4P26JIwojDk0QPUOcRr cPFONNxucDV4FJTArTPhCdnIlPd0JjI7glBpkwKGVPCEYcDjOCyKCSObwudjf11xeLDM 7O7GMneZJpK/8aKFUi3X2ndnja0MAzlhIMcgI= Received: by 10.180.224.4 with SMTP id w4mr1734468bkg.174.1225099991861; Mon, 27 Oct 2008 02:33:11 -0700 (PDT) Received: by 10.180.224.18 with HTTP; Mon, 27 Oct 2008 02:33:11 -0700 (PDT) Message-ID: Date: Mon, 27 Oct 2008 11:33:11 +0200 To: "Lester Caine" Cc: "PHP internals" In-Reply-To: <49047D62.1030900@lsces.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49047D62.1030900@lsces.co.uk> Subject: Re: [PHP-DEV] RE: From: tudor.prodan@gmail.com ("Tudor Prodan") Well, given how much PHP has copied from C (and I mean that in a good way), why not copy the sane, less-controversial namespace separator and behavior that we all know and love? \Tudor On Sun, Oct 26, 2008 at 4:23 PM, Lester Caine wrote: > Tudor Prodan wrote: >> >> PHP has to be unique, using the double colon notation would be too >> cliche, but if we're not respecting conventions, why not go with >> something more exotic? I've always liked the o with the slash trough >> it. The e with the horizontal colon is also pretty nice. The n with >> the tilde over it, it so strongly says _n_amespace. >> >> When I read this message first thing I did was check the date, but >> deep down I knew it wasn't April yet. >> >> One of the top reasons why I hate using windows consoles is the >> dreaded "\" character. >> >> Each and every keyboard model I have has this key in a different >> place, sometimes one hard to reach. Every time I'm in doing a cd in >> windows I press 2-3 other keys while going for the backslash. >> >> That whole rating table over on the PHP wiki is just ridiculous. >> - type-ability: come on. If anything, it should get -1 there >> - typo-vulnerability: pretty big, but I think most problems will be >> escaping rather than typos anyway >> - number of chars: any sane person will agree that you can write >> "::" a lot faster than "\" >> - editor integration: not really, many editors will have trouble, >> including vim >> >> I eagerly await namespaces in PHP, but guys, if you don't have a good >> idea, I think copying is better than implementing a bad one. > > Tudor - There is little point reiterating half of the facts. There are very > good reasons why - for PHP - a simple solution was not working. MANY people > were coming up with problems as to why the currently implemented 'solution' > was only going to create a black hole at some point, and what ever was doing > to be done was going to cause problems somewhere. > > The backslash is not ideal, but I think we all need to get behind it rather > than complaining. The only other real alternative today is to shelve > namespaces altogether for the next release rather than putting something in > that is simply not practical to extend later? > > Given the polarised views a total solution that everybody could agree with > was just not happening! > > -- > Lester Caine - G8HFL > ----------------------------- > Contact - http://lsces.co.uk/lsces/wiki/?page=contact > L.S.Caine Electronic Services - http://lsces.co.uk > EnquirySolve - http://enquirysolve.com/ > Model Engineers Digital Workshop - http://medw.co.uk// > Firebird - http://www.firebirdsql.org/index.php > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >