Thank you very much for these somewhat insighful words of wisdom.
Now I have spent the last 2 weeks assessing the possible means I had to
acheive my goals, trust me when I say that global variable was far from the
first on my list of alternatives. But the fact of the matter remains, I need
lists of data, an array or a linked list, whichever, and I need that list
available throughout the rest of the packages somehow.
Now instead of stopping your comment at telling me that this design is
bad, that global variables bring global famine, let me assure you that list I
am talking about is NOT a food shopping list :-). Why dont you detail
yourself and bring me the other alternatives and possible solutions. If you know
of a way to obtain this availability without the use of global variables then
please, by all means, do let me know so that I may do this the right way.
In other words, dont stop at telling me this is a bad design. Contrary to
popular belief global variables are a bad design pretty much in any
programming language. Tell me why it is bad, and how to make it better.
> What you are talking about is a global variable. Global variables cause
> disease, famine, and war, not to mention really badly designed,
> impossible-to-debug software. The first rule of software engineering is
> modularize and never use global variables. The first two rules of
> software engineering ...
> Jeff Carter
> "Nobody expects the Spanish Inquisition!"
> Monty Python's Flying Circus
[log in to unmask]
Sent through GMX FreeMail - http://www.gmx.net