Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41306
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 64.99.136.138 as permitted sender)
Message-ID: <006c01c93362$ca3c4990$3ffc1f3e@foxbox>
To: "Arvids Godjuks" <arvids.godjuks@gmail.com>,
	"Stan Vassilev | FM" <sv_forums@fmethod.com>
Cc: <internals@lists.php.net>
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> <9b3df6a50810210117n5f387b91tb9cb04d48db72037@mail.gmail.com>
Date: Tue, 21 Oct 2008 10:52:52 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Namespace issues
From: steph@php.net ("Steph Fox")

Hi,

>> Guys, this is like junior school in here.

Yep.

>> Let me put some things in perspective:

No, let me. Greg worked his butt off the entire weekend looking for the 
flaws in *all* the options available to us, including a couple of new ones 
that never even reached the list before he rejected them on technical 
grounds. Thanks to his efforts, we already have a pretty good picture of the 
strengths and weaknesses of each approach - and as should be obvious to all 
by now, there is no perfect solution. Whatever we chose, it's a compromise.

What we're hearing here about European keyboard layouts is useful info 
because it gives some idea of how popular/unpopular the backslash would be 
as a solution and why, but it shouldn't carry as much weight as the 
accessibility argument against the triple colon. One is liveable, if not 
optimal, whereas the other is plainly not liveable for some. We've already 
heard two workarounds for the backslash issues, but there are none at all 
for ::: + imperfect eyesight.

Clarity and simplicity are the two chief requisites. We're all fully aware 
of that, from Engine developer to n00b, so there's really no point in 
discussing it to death on-list at this stage.

- Steph