Kent Johnson wrote: > ---- Dinesh B Vadhia <[EMAIL PROTECTED]> wrote: > >> Consider a data structure (say, an array) that is operated on by a bunch of >> functions >> >> The described way is to place the statement 'global' in line 1 of each >> function. On the other hand, wiser heads say that the use of 'global' is >> bad and that reworking the code into classes and objects is better. >> >> What do you think and suggest? >> > > Yes, global is bad. > > - Pass array_G as a parameter to each function > or > - Make all three functions methods of a class with array_G as an attribute. >
Global is almost always bad. Sometimes you can make a valid argument that information truly has a global context, such as a debug flag, or the parsed options that were passed from the command line. Different philosophies... > Kent > >> Dinesh >> > > _______________________________________________ > Tutor maillist - Tutor@python.org > http://mail.python.org/mailman/listinfo/tutor > _______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor