Download

Section categories

ActiveX [655]
Components and Libraries [747]
C and C++ Tools and Components [189]
C and C Tools and Components [141]
Databases and Networks [645]
Delphi Tools and Components [455]
Editors [111]
Help File Tools [120]
IDEs and Coding Utilities [167]
Java [194]
JavaScript [62]
Misc Programming Tools [545]
PowerBuilder Tools and Components [27]
Registration Tools [49]
Setup Utilities [160]
Visual Basic Components A-G [134]
Visual Basic Components H-P [72]
Visual Basic Components Q-Z [63]
Visual Basic Tools [163]

Our poll

Which Is The Best Browser?
Total of answers: 3

Statistics


Total online: 28
Guests: 28
Users: 0

Login form

File Catalog

Main » Files » Programming » Visual Basic Tools

PrivateI 0.916
29.01.2011, 04:39
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.

Category: Visual Basic Tools | Added by: File-Post
Views: 98 | Downloads: 0 | Rating: 0.0/0
Total comments: 0
Only registered users can add comments.
[ Registration | Login ]

Search

Site friends

add site