Why can't we stick to consistency ? PHP (classes, functions,
interfaces, abstracts, etc) are all done the same way. What is the
"need" of changing this ?

I see reasons like :

- I don't like indentatation (Answer to that: PHP must make you quite
sad then... and I can't imagine what python makes you feel like...)

So I think what we should do here is either reassemble the ideas (That
were of course lost since the initial discussions).

- Why did we want to call it a package ? Simply because it behaves
exactly like packages ?
- Why do we decide to have a whole new way of declaring namespaces ?
(IE: No braces)
- Since we decided to have "namespaces" what is "so" bad about having
nested namespaces?

Do we want to be "that" different from others? I think having a
solution that looks a lot like other software languages is something
that will not only bring us users but also bring us a lot of love from
other language developers (when they have to use PHP (because yes,
some have to use other languages)).

Greg came up with a pretty good patch for multiple namespaces per
file. However it does not follow the "PHP Coding Practices" - In terms
of style and characters used.

Greg? Stas? Dmitry? Could we get a "resume" of the backstage talks you
guys spoke about? I'm sure you did so just a little taste to inform us
all of "why" we decided to change PHP's general syntax would be
awesome :)

Thanks,

D

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

Reply via email to