🚀 go-pugleaf

In article <1189@ncis.tis.llnl.gov> turner@lance.tis.llnl.gov (Michael Turner) writes:
>I've explained to many programmers my view that global variables are to
>data structures what the GOTO is to control structures (worse, in many
>ways, if you ask me--I'll use the occasional GOTO, but my references to
>global variables tend to be to someone else's, not to any that I invented.)

  Global variables : data structures :: LongJmp : control structures

The problem with global variables is that they can affect anything,
anywhere in the program.  Thus, it's difficult when you see an
assignment 'FLAG = 1' to figure out what in the world this might
affect.  (Comments help, too, but....)

>When is a global necessary?  I think the answer is: almost never.

  They're almost never necessary, but they can be convenient when
working with languages which don't have nesting.  If I read in N, M,
and two N-by-M arrays, I'm likely to use a global variable to hold
this, instead of passing an extra four parameters to 90% of my
procedures.  It's sloppy, but....

  I prefer working with languages which have nested scope; in that
case, I can pass parameters in once, and use them in subprocedures
without needing to explicitly pass them.  This can be abused, just as
globals can, but often it's more clear, IMHO, than explicitly passing
parameters--it may be more clear to call a function 'edge(X,Y)' in a
test than 'edge(G,G2,N,M,X,Y).'

>Forget about GOTO-phobia, how about "`extern' variables considered
>harmful?

  And static variables!  And global error statuses!  <grin>

	Anton
   
+---------------------------+------------------+-------------+
| Anton Rang (grad student) | rang@cs.wisc.edu | UW--Madison |
+---------------------------+------------------+-------------+