Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41439
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain vector-seven.com from 67.207.131.5 cause and error)
Message-ID: <4905A81F.3070506@vector-seven.com>
Date: Mon, 27 Oct 2008 22:38:07 +1100
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Arvids Godjuks <arvids.godjuks@gmail.com>
CC: Lester Caine <lester@lsces.co.uk>, 
 PHP internals <internals@lists.php.net>
References: <d1bff87d0810260351n4361e42n62b86165ef56c70@mail.gmail.com>	 <49047D62.1030900@lsces.co.uk> <49059FC1.2060702@vector-seven.com> <9b3df6a50810270411t2b8e050au33d68564225311d4@mail.gmail.com>
In-Reply-To: <9b3df6a50810270411t2b8e050au33d68564225311d4@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RE: </endnamespacediscussion>
From: tom@vector-seven.com (Thomas Lee)

I disagree that PHP being a dynamic language justifies the introduction 
of deeply unpopular syntax. I mean, PHP developers are your end users. 
Bad past design decisions aside, you don't want to alienate your users.

And yes, this has probably been argued in the past. Unfortunately, it 
looks like you have people's attention *now*.

You're also right in that we can choose another language. I just wonder 
why you'd be so eager to encourage it.

Anyway, my point is that there may be other options. Such as putting off 
a long-sought feature until it can be implemented properly.

Cheers,
T

Arvids Godjuks wrote:
> 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
>>
>>
>>     
>
>