Using globals is kind of like leaving your dirty dishes in 
the sink.  Everyone agrees it's bad, but they do it anyway.

With a bit of thought, there is almost always a good way to
modularize your code.  C++ makes it easy, and with C I 
usually end up defining a bunch of structures that are 
passed around.  Perl makes it harder but you can do it.

Cheers,

-- Rod
   http://www.sunsetsystems.com/

On Friday 20 September 2002 11:47 am, Peter Jay Salzman wrote:
> ...
> that's quite interesting; obviously a lot of thought went into those
> ideas.
>
> but i can certainly imagine option 5 (data coupling) being detrimental
> to code maintenance.   when you look at a screen and see a thick dense
> blob of code everywhere.   kind of like how perl can get.  as in, you're
> normally black xterm background looks completely white when you don't
> have your glasses on.
>
> to be honest with you, i asked this question because someone challanged
> me to argue the point of "globals are bad".   other than the 2 reasons i
> gave above and the fact that it's conventional wisdom, i really can't
> come up with much.  i was hoping to get some ideas.
>
> pete

_______________________________________________
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Reply via email to