>...I go one or two steps further: no PRIVATE variables and no PUBLIC properties either, any changes
>in the state of an object should be accomplished by sending a message to it, never by assigning a
>value to a property (which should be protected anyways, or even hidden).


Within the confines of the limited power of the Visual FoxPro debugger, such constraints may be valid. In a modern full-featured language and debugger, such constraints are no longer required.

It should've been the goal of Microsoft all along that the developer is in control, not held back by artificially imposed limitations.