>> If I were naming variables across classes I would choose to name them the same if they were to hold the same type data and be of the same data type. I would name them differently otherwise. <<
It's not for nothing that even though "private" variables are supposed to be totally "invisible" that there is still so much written about naming conventions. Many companies have whole guides on how to name and type variable using C++, Java, etc. Even when you can be sure that one variable is not going to tromp another, it's still MUCH easier to maintain, especially when the original programmer is not necessarily going to be available to deal with it. ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
