On 13.03.2009, at 00:39, Andrei Zmievski wrote:
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.
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.
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.
Just a gentle reminder to make sure we don't miss this..
So where are we at here?
If nobody proposes something, this will just slide by ..
I guess we can say that there is a definate risk, that eventually
extensions will become namespaced. Same for internal functions.
So calling a namespace "Date" or "str" is probably not a good idea ..
right?
Now for the less obvious stuff .. does the ZF prefix all their top
level namespaces with ZF etc.?
Speaking of ZF ... wasnt there an effort over at ZF to define a
sensible standard?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
