> Setting vars to void on purpose makes absolutely no sense to me. It > never has and it probably never will. Void means "I haven't even been > touched by code yet, so don't use me", while some other value (0 pr > #null or "") means *something* has manipulated the variable and the > person who wrote the code stands a reasonable chance of knowing what > its value is (or should be) from line to line in the code that handles > it. That implies a programmer who knows what his code is purportedly > doing at all times, and it's the kind of person I'd be more likely to > want working on a project.
I pretty much agree. But let me play devil's advocate. When I kill an object, a timeOut, a MIAW, or something else I want to be rid of permanently, is there a harm in setting the holder variable to void? I know the same thing can be done by setting the variables to 0, but is there any harm in voiding them? That's assuming, of course, that you (1) won't be using the variable again, or (2) you know that, if it's void, the object doesn't exist. Can I work on your project? ^_^ Cordially, Kerry Thompson [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
