Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:11666
Return-Path: <aidan@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 46431 invoked by uid 1010); 30 Jul 2004 13:38:10 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 46387 invoked by uid 1007); 30 Jul 2004 13:38:10 -0000
Message-ID: <20040730133809.46346.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <10911429306360000@9866357972520000.9866341568840000> <00b101c47623$78bcd270$0a00a8c0@home.jevon.org>
Date: Fri, 30 Jul 2004 23:38:15 +1000
Lines: 20
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Posted-By: 144.132.77.185
Subject: Re: [PHP-DEV] GOTO operator
From: aidan@php.net ("Aidan Lister")

> Develop some wacky construct that you have to use instead... that way, it
> will scare off novice users, and expert programmers will HAVE to know what
> they're doing and know that they really need it before they have to
> implement it. It's along the lines of "make the most dangerous stuff the
> hardest to do".

I think this is probably one of the best ideas...

> I'm not sure how, though... a huge language construct
> (goto_this_line_please)? Use numbers instead of labels? Relative jumping?
> Require extra messages? A weird symbolic construct? *shrug*

I'd just disable it by default, force them to compile --with-goto

That definitely stops the novices, and allows experts to use it if they
reallllly need it.

Of course then portability then becomes a problem...