>>>>It is very easy to totally eliminate this potential problem forever, simply NEVER USE PUBLIC VARIABLES and this problem will NEVER happen.
>>>
>>>Would the problem still exist if the public variables were RELEASEd properly? Creating a public variable and not releasing it sounds like more of a bad programming practive than using a public variable.
>>
>>Can you point a case where PUBLIC was the only solution?
>
>I can not think of anywhere I use a PUBLIC var. Even my global app object that has to be visible to all objects in my app is scoped as PRIVATE. However, the var is created in my MAIN prg.

Same for me.

To use a PUBLIC variable, you have to declare it explicitly.
Even a lazy programmer who create variable on the fly use PRIVATE as it is the default scope.

:-)