[prev in list] [next in list] [prev in thread] [next in thread] 

List:       php-internals
Subject:    Re: [PHP-DEV] Reserved namespaces
From:       Greg Beaver <greg () chiaraquartet ! net>
Date:       2009-01-26 13:44:48
Message-ID: 497DBE50.40304 () chiaraquartet ! net
[Download RAW message or body]

Alain Williams wrote:
> On Mon, Jan 26, 2009 at 01:06:01PM +0100, Christian Schneider wrote:
>> Things gettings reserved at a later stage (like originally keywords, now
>> namespaces) can lead to a big deal of frustration. Therefore I think it
>> is crucial to have a clear naming guide now.
> 
> +1
> 
>> And these guidelines have to be noticed by everybody who starts to use
>> namespaces so they have to be placed prominently.
> 
>> Personally I'd even prefer them to be enforced in code so they can't be
>> missed.
> 
> No:
> * there are occasional times when rules might want to be broken
> * to enforce it just makes the language/compiler bigger
> * If it is advertised and someone breaks the rules - then it is their problem.
> 
>> Removing restrictions later on causes less trouble so I wouldn't mind
>> too much if a couple of namespaces (or namespace prefixes) are reserved
>> but never used.
> 
> As I suggested, do it the way that perl does: it is keyed off the case of the characters.
> So, the reserved spaces could be one of:
> 
> 1) entirely lower case (or perhaps just start with lower case)
> 2) entirely upper case

People, can we all agree to remember that PHP is case-insensitive with
the exception of variable names and a few constants?

Thanks,
Greg

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

[prev in list] [next in list] [prev in thread] [next in thread]