|
|
|
PrivateI analyses a Visual Basic project and reports the variables and procedures that have been declared Public but are in fact Private or unused. Keeping the components of a module Private is a good thing. When variables are kept local to a module they cannot have their value changed outside the module making it much easier to keep track of them. When Subs and Functions are kept local to a module there is no concern about parameters being passed from outside the module. The more a module contains Private components the less reliant it is on external code and becomes more portable, robust and easy to maintain. Private is good.
| Platforms: |
Windows 95, Windows, Windows 98, Windows Me, Windows NT, Windows XP, Windows 2000 |
|
|
|
|
PrivateI User Reviews
