Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41382
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.123 cause and error)
Message-ID: <49047D62.1030900@lsces.co.uk>
Date: Sun, 26 Oct 2008 14:23:30 +0000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080829 SeaMonkey/1.1.12
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <d1bff87d0810260351n4361e42n62b86165ef56c70@mail.gmail.com>
In-Reply-To: <d1bff87d0810260351n4361e42n62b86165ef56c70@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RE: </endnamespacediscussion>
From: lester@lsces.co.uk (Lester Caine)

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