>>>>It is not a clean solution.
>>>>After subprocedure header, and before private variable is declared, public variable is not hidden and it is accessible.
>>>
>>>Then put it in the header: name your parameter the same as the public variable. Of course, you will completely confuse yourself and anyone looking at the code, but you won't be able to touch or see PubVar :).
>>
>>You are very close. But you use the name of the variable in subroutine header. So, how to do it without even mentioning PubVar in the subroutine?
>
>Now I'm very far... even using "local all like *" leaves you open between the header and that line.
>
>Fabiooooo! What's he talking about?

I think Yuri talk about a wide security program.
What is interesting on a conceptual level, but in practice it is not manageable.
Yuri wants a sort of protection between different programmers.
To do this you should attach to the variables of rights of use by subroutine created by different programmers,
( like NTFS ACL ).
This could generate more control over programming,
but in my opinion makes development impractical.

Despite the myriad attempts at automatic documentation and meta-languages
​​for describing the meaning of the software written,
the reality is that what really works is that the programmer is able to keep in his head.