Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41435
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.172 as permitted sender)
DomainKey-Status: bad
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:references;
        b=V8umYKv4Hr7q89N1A5c4NNn4nt7TBLLuNW8xMUdIRF38/HQ8NpSuKtgcPh1TyBB6PK
         f4wtIDy8j4vF02grE+6RWMEJE4xQWRJrJ7ZqPv0NYD++vqHnjA9SZlOq+HqOdDkNmdH1
         yAS+3KZNtfjMiEm3BOdFTG4o7xPTRPtDZ8rzU=
Message-ID: <9b3df6a50810270411t2b8e050au33d68564225311d4@mail.gmail.com>
Date: Mon, 27 Oct 2008 13:11:36 +0200
To: "Thomas Lee" <tom@vector-seven.com>
Cc: "Lester Caine" <lester@lsces.co.uk>, 
	"PHP internals" <internals@lists.php.net>
In-Reply-To: <49059FC1.2060702@vector-seven.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_16236_2841275.1225105897055"
References: <d1bff87d0810260351n4361e42n62b86165ef56c70@mail.gmail.com>
	 <49047D62.1030900@lsces.co.uk> <49059FC1.2060702@vector-seven.com>
Subject: Re: [PHP-DEV] RE: </endnamespacediscussion>
From: arvids.godjuks@gmail.com ("Arvids Godjuks")

------=_Part_16236_2841275.1225105897055
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

This was argued for months, there was tons of emails to read and backslash
is best for most people. PHP is dynamic language - that makes some major
restrictions, so you just can't apply something that is already in use
easily. That's why :: was rejected in first place. That's why . was
rejected, other separators had other issues. Backslash is easy to see, easy
to type (most layouts have it without Shift or something else) and clearly
says - I'm a namespace!
So anyway - in any language you will find something that you would't like.
You just live with that or chouse another language. That's all.

2008/10/27 Thomas Lee <tom@vector-seven.com>

> Lester Caine wrote:
>
>> 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?
>>
> I'd prefer to see it shelved for another release with the aim of fixing
> whatever technical barriers made the syntax unworkable in the first place.
> I'm sure you'd have plenty of volunteers.
>
> My personal concern is that once this goes public, we (the end users) are
> stuck with that decision for the forseeable future.
>
> I think there's obviously enough unhappy campers here that this option
> should be at least considered. Not that I'm holding my breath or anything.
>
> Everybody seems to be getting awfully emotional about this ...
>
> Cheers,
>
> T
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

------=_Part_16236_2841275.1225105897055--