Re: Request for comment

The concern that should be addressed however with changing the behavior of a construct such as foreach (which I use heavily in all my code i've done with 4) is that you risk the chance of breaking someone's code. Most people who download a version upgrade will not be aware that the foreach construct has changed... just make sure the change is well announced and well documented to avoid problems. ----- Brendan W. McAdams | ph. (305)377-2880 email: brendan@plexmedia.com | cell: (305)218-6466 Programmer/Systems Administrator | pager: (305)277-4879 Plexus M/2, Inc. | fax: (305)377-2870 http://www.plexmedia.com "Always listen to the experts; they'll tell you what can't be done and why. Then do it." - Robert A. Heinlein ----- Original Message ----- From: "Zak Greant" <zak@php.net> To: <php-dev@lists.php.net> Sent: Thursday, August 10, 2000 6:31 PM Subject: Re: [PHP-DEV] Request for comment Andi wrote: >[snip] >Does anyone see a problem with this? It would mean you can't put obscure >stuff into foreach(). The only issue that I can see with this is that foreach's behavior would not be consistent with the other looping constructs. However, I personally do not feel this is a big problem. After all, PHP is not Perl ;) - Zak -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net