On Tue, Oct 28, 2008 at 11:17 AM, Steph Fox <[EMAIL PROTECTED]> wrote: > Hi Marius, > > Don't know i never saw something so ugly since c++ templates syntax > I find it funny that php is designed by committee and no one listen to > the community > === > > You have written to this list a few times before. Here's a brief summary of > your posts: > > 1) We should be moving to git not svn > 2) We should drop $ for variables because it makes PHP 'bloated' > 3) Mingw compilation (which we don't support) fails > 4) If we want your help supporting firebird under Windows we should build it > and send you a report > 5) We're on slashdot (for \) > > === > And the team continues even if is an bad decision (they call it > technical one) if you see it from the point of view of syntax elegance > it's not so pretty even c++ looks better . > === > > I'm not even going to comment on that. > > - Steph yes is true that i like to have strong opinions and yes i could be wrong in most of them but when all the comunity screems at the namespace issue i think core developers should be more diplomatic and offer the good solution not close the eyes and wash the hands and go forward
an semisolution would be an php.ini variable like NAMSPACE_SEPARATOR="::" so if you have an issue with your classes can be reset to "\" or whatever with ini_set i think it's easy to be done if i look at the patch that created the backslash separator issue http://pear.php.net/~greg/backslash.sep.patch.txt > > > > -- developer flamerobin.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
