> I think Jakob's point is well made, but the really important thing is not to > be accountable when someone says "My code broke and we lost the > gig/contract/bonus because your code forgot to reset the itemDelimiter".
Probably the best point. People never live up to standards. You can apply the reverse of the chair analogy - expecting everyone to put the chair back in the hopes that when you sit down without looking, the chair will be there, is similar to expecting everyone to check if the chair is there before they sit. "Always check for the chair, and always return the environment to the state it was in before you sat down," is good advice. I agree with Jakob that you should always set the itemdelimeter before use, but not setting it back to its previous value is a bit like leaving orphaned objects in memory... if you affect a change in the environment, you should clean up behind yourself. This is not to say that not setting the itemdelimiter before use is not sloppy coding (or using 3 "nots" in one sentence is not sloppy grammar), but as they say in the woods, "pack out what you pack in". -Kurt [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!]
