Mailinglisten-Archive |
ich weiss nicht, in wiefern jemand hier die internals mailingliste von php.net verfolgt... dort laufen seit gestern abend eine interessante diskussion bzgl. goto statements... was haltet ihr davon? sinnvoll, oder schwachsinn... ? gruss thomas > -----Ursprüngliche Nachricht----- > Subject: Re: [PHP-DEV] GOTO operator > From: andi at zend.com (Andi Gutmans) > Newsgroups: php.internals > To: ilia at prohost.org,internals at lists.php.net > > At 01:29 PM 7/30/2004 -0400, Ilia Alshanetsky wrote: > >On July 30, 2004 01:11 pm, Andi Gutmans wrote: > > > Secondly, I just don't understand what the sudden > necessity for the > goto > > > construct is when over the years we have barely ever had a PHP > developer > > > asking for it. > > > >That can be said for virtually any new functionality that > was added to > PHP. > >Looking at the feature request lists, I only see one person > asking for > >exceptions to be added to PHP, and yet they were added. As PHP's > userbase and > >it's possible applications grow so do demands of the developers from > the > >language. Just because something was not needed for X years, it does > not mean > >there is no need for it now. The comments expressed by a large number > of > >responders to this thread indicate that "goto" are not a fancy of a > slim > >minority. > > 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. > > Andi
php::bar PHP Wiki - Listenarchive