Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:11639
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 29 Jul 2004 19:04:49 -0400
Reply-To: Jason Garber <jason@ionzoft.com>
Organization: IonZoft, Inc.
Message-ID: <366856364.20040729190449@ionzoft.com>
To: internals@lists.php.net
In-Reply-To: <41099925.4020700@hristov.com>
References: <20040729021337.73894.qmail@pb1.pair.com>
 <1091136355.490.4.camel@localhost> <1091139076.29517.12.camel@blobule.suds>
 <410991E1.6070000@hristov.com> <1091140927.29516.18.camel@blobule.suds>
 <41099925.4020700@hristov.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] GOTO operator
From: jason@ionzoft.com (Jason Garber)

Hello,

  After thinking about it for a bit, I'm convinced.  If goto can be
  implemented so that it is fast, and does not adversely affect other
  parts of PHP, by all means, do it.

  Andrey, you've been very clear why you would not use it, but why do
  you want me not to use it?  I can think of quite a few times when it
  would have made my code much cleaner.

  As far as shooting yourself in the foot, how about:

     mysql_query("SELECT x,y,z FROM t WHERE id=" . $_GET['id']);
  or
     include($_GET['header_file']);
  or
     shell_exec('somecommand ' . $_POST['param']);

  There are PLENTY of way's to shoot yourself in the foot with any
  language.  If joe shoots himself in his foot, does that mean that
  I should not be allowed to shoot at all?

  +1

-- 
Best regards,
 Jason                            mailto:jason@ionzoft.com