Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:11763
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Sat, 31 Jul 2004 14:38:57 +0200 (CEST)
To: Aidan Lister <aidan@php.net>
cc: internals@lists.php.net
In-Reply-To: <20040730133809.46346.qmail@pb1.pair.com>
Message-ID: <Pine.LNX.4.58.0407311438390.14661@localhost>
References: <10911429306360000@9866357972520000.9866341568840000>
 <00b101c47623$78bcd270$0a00a8c0@home.jevon.org> <20040730133809.46346.qmail@pb1.pair.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] GOTO operator
From: derick@php.net (Derick Rethans)

On Fri, 30 Jul 2004, Aidan Lister wrote:

> > 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...

So this is yet-another-bogus-idea ;-)

Derick