Re: GOTO operator

At 07:48 PM 7/30/2004 +0200, Edin Kadribasic wrote:

a) Most of the OOP functionality was requested by a huge amount of PHP developers I've talked to. b) I don't think internals@ is a reflection of the PHP community. Most people here fall into the category of very advanced developers. Doesn't make sense to me to add a stinky construct which no one should really be using, just because there are 50 people out there (most of them on internals@) who would actually use it correctly. Come on. I can't even believe we are arguing about this.

I really can't believe this "PHP is only for morons" attitude that comes from time to time here on internals.

It's not only for morons but the PHP spirit has always been to keep away of un verbose and unstructured crap like you can find in Perl and friends. I think the "goto" statement fits in that category and you guys are exaggerating the necessity of it both due to it making no sense from a performance aspect (which was one of the arguments) and as the most common use of goto which is breaking out of nested loops also doesn't hold water. So what's left? All of the generation stuff? Those tools can work a bit harder when they are doing machine auto-generation of code and survive. The abuses of the goto statement are far greater than the uses, especially in a language like PHP. Andi