>>>Why redefine private scope to local ?
>>Visual FreePro defines a _caller object which is able to access data in functions on up the
>>caller stack. Private variables are local variables in function, but they are not visible through the
>>_caller object. This allows code executing at a given point to isolate its data from external reference.
>
>Maybe a new keyword like "Hidden", which is known from properties is better than redefining private
>in memvars. Any ported stuff will throw errors in the compiler, not hard to trace behaviour differences
>in the runtime if one instance is overlooked.


Visual FreePro adds a new command ON COMPATIBILITY DO compatibilityHandler which operates like ON ERROR in that any time the runtime execution engine encounters source code which is no longer supported the same way, it calls ON COMPATIBILITY. The ON COMPATIBILITY parameters include an explanation of the cause, along with the proposed workaround.