>Technically, yes. But if I declare a variable as PUBLIC, anyone will understand that I mean it to have public scope. If I declare it PRIVATE, some may wonder if it was intended to be private from a higher level or is just a programming issue.

Sorry Vlad but violate the correct use of a command because it looks better? Declare variables public so that programmers who don't understand how memvars work won't get confused? I am sorry but I can't ever agree with this statement. I find it hard to believe that you said this.

>>I propose that using publics is a bad design in itslef.
>
>I know. :) And I agree with you (for my own applications). But this doesn't mean any other design that uses public variables is bad.

I said and still say that using PUBLICS for the purpose they were created (to have their scope outlive the routine that created them) is BAD design. And using a PUBLIC declaration where it is not required is also BAD design. So if you need a public it is a sign of a design problem and if you don't need a public but make one anyway is also a sign of bad design.