Re: GOTO operator

> 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...