Polisher helps you refine your code

Polisher

Polisher gives you a wide choice of formatting options to professionalize and standardize your code output. You may set the indentation, and the number and placement of blank lines for any code structure or comment style. Multiple line declarations may be split - listing each declaration on it own line, while the As statements are aligned in a column of your choosing. Single line If statements may be split into an If block structure.

Code instructions such as Option Explicit may be inserted, and Next variables removed. Using Polisher you may set the order precedence of Declare Statements, Procedures, and local Declarations within the code file structure. Another big plus, Polisher will spell check the input and output files, based on your pre-defined preferences.

Polisher Features

General Formatting

Polisher can add 'Option Explicit' to require variable declarations, and align declarations as clauses in one column. It can split multiple variable and 'Const' declarations, multi-statement lines, and single-line If statements, and split variables from code (e.g., numError: Resume Next). It can also automatically remove optional variable names from the Next statement, and manipulate line continuations in those dialects which support them.

Spell Checker

The Polisher can check the spelling of standalone and embedded comments, and/or text in the form definition found in properties such as 'Caption', 'Text', and quoted literals. The user can instruct the spell checker to ignore words with all caps, words containing numbers, and Visual Basic key words. A custom dictionary can also be created.

Code Line Indentations

Polisher can indent all of the code, none of the code, only the declarations, or only the baselines. It can indent Case statements either 1 or 1/2 level to the right of the 'S' in Select Case, or align the 'C' in the Case statement with the 'S' in Select Case. It can align the 'E' in the Else statement with the 'I' in the If statement, or indent Else statements one half level to the right of the 'I' in the If statement. The size of indentations is user-defined.

Conversion

Polisher can do a number of code conversion techniques to ensure that your code stays up-to-date and runs well. It can convert DAO 2.x database references to DAO 3.x, as well as insert intrinsic constants. In addition, it can convert Global to Public and Dim to Private in the General Declarations section of any file.

White Space

Blank lines can be ignored, removed, or automatically inserted before or after the beginning or end of control structures. A user defined number of consecutive blank lines can be removed as well.

Comment Formatting

Stand-alone and in-line comments can be left intact, removed, or automatically indented to a specified column. In-line comments can also be automatically indented to the indent level of the next or prior line.

Comment Block

Different comment blocks can be inserted at the Module Level, for User-Defined Procedures, and for Event Procedures. The Polisher can position comment blocks before or after the start of procedures. Prototype comment blocks may have fixed and variable text. The latter is provided by substitution variables and user input.

Debugging

To aid in debugging and maintainability of your code, Polisher can insert line numbers by module, procedure or project. (Existing line numbers replaced); insert error trapping code; insert proc entry/exit code; and identify untyped functions.

Y2K Checking

Analyzes code for Y2K (Year 2000) problems. All code is checked for date functions (Day, Month, SerialDate, etc.) and data names that include the word date (StartDate, EndDate, PayDate - but not Update).

Polisher is part of the Triple Bundle

Home || Shopping Cart || Site Map || Newsletter/Blog
Search HALLoGRAM || Request More Information
CALL TOLL FREE 1-866-340-3404