>>I propose that using publics is a bad design in itslef.
>
>PMFJI -- but why? I have never bought the "just because it is" or "because such and such famous guru says so" or "because it is accepted practice" arguments. There has to be a reason - and not that there isn't one here - I just haven't seen it listed (unless I missed something in the thread)
>
>BTW - I use only one public variable - to hold my app object. I ask you to tell my why using one private var instead would be better in any way - performance, maintanability, security, stability, etc.?
>
>Ken

Ken,

Happy New Year!

I'd bet that most folks would have no problem with your approach. Even then you could create your app object and pass it into your system and reference it locally to eacj object. That's what I do and the reason is that it more closely follows the notion of each object being able to sustain itself.

Seems to me that whe whole idea is to use this object oriented stuff to make our apps easier to maintain and PUBLIC variables are, well, messy compared to this new capability. Mind you I've used them since late 1986, early 1987 so making the transition to using an object was something I had to think through first. Now I wouldn't develop any other way.

Just one take.

Best,

DD