Hello, I don't know if chiming in at this point has any merit, but here is what I see.
We have many, many people in favor of goto and ifsetor. They see much legit use for those constructs. Then, we have others who say that it will result in spaghetti code. This is a completely invalid point because we have all seen spaghetti code in PHP already. Spaghetti code comes from an inexperienced or sloppy developer, not from cool language features. When considering what language to use in my company, I looked at the community and open-development that surrounds PHP. These are some of the reasons that I chose PHP. I am still very happy at that choice. The biggest thing that I see working against PHP is individuals who say "I don't see myself using xxxx, so you should not be ALLOWED to use xxxx." That being said, we need carefully evaluate the plusses and minuses of adding a feature: Is it's use clear? Does it reduce the speed of PHP? Does it open bizarre security holes? Is it useful by a reasonable percentage of developers? Does it solve a common problem or annoyance present in PHP? Does it add additional problems or annoyances to PHP? All in all, I think if everyone stops being religious about goto, and logically evaluates it, we can quickly come to a conclusion. -- Best regards, Jason mailto:[EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
