RE: No Subroutines (was Re: Debugging many subprocedures)

> First, the hard-science programming side of it: If
> your language provides an IF/ELSE/ENDIF and a LEAVE
> operation for looping constructs, then you should
> never need a GOTO.

Since this thread is winding down, perhaps a trivial
alalogy wouldn't be too far out of line.  Say you're
playing Monopoly, the game from Parker Brothers, and
your player is looping around the board when it
unexpectedly lands on the square that says "Goto
Jail".  Would that be hard to understand?  Would it be
more clear if stated differently?

> There are few things I am adamantly opposed to
> because of their intrinsic nature.  But be
> consistent and use common sense, and you'll be okay.

This sounds like good advice.  If the code is easy to
read, what's the big deal?

Nathan.



                
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs