WB 2017C Dec 28, 2017
DLL 6.17cqc First showing up in WB 2017C
Replaced copyrights, icons and embedded images.
Modified uninstall program to account for multiple paths in the
TEMP and TMP environment variables.
WinBatch Studio:
Fixed unhandled exception in WIL file type syntax coloring.
Fixed memory corruption problem in output window implementation.
This release of WinBatch Studio includes the new Lexical Analyzer module:
Added an 'Analyze' menu item to the debug menu bar menu. Select this menu item to
invoke the Syntax Analyzer on the current foreground document. The Syntax Analyzer
tool scans the current script for syntax errors without actually executing the script.
Any errors are displayed in the "Syntax Analyzer" tab of a WinBatch Studio output
window automatically displayed by the Analyzer.
Each error line in the Analyzer window represents one error. A single line in the
script can produce more than one error. Error lines consist of a full path-name of the
file being analyzed, the row and column numbers of the error's location in the script,
the word "error" or "warning", an error number, and a brief error description.
Using your mouse to left click on an error in the Syntax Analyzer window will set the
WinBatch Studio input cursor to the beginning of the line in the current script that
contains the error.
A few thing to remember when using the Syntax Analyzer:
Variable values are not checked because the script is not executed.
The Analyzer cannot determine the resulting syntax of substituted variables.
The grammar of function parameters is checked but not the correctness of parameter
values.
The Analyzer can be used on WIL menu files but menu names line generate "unexpected
item found online" errors. Ignore these errors.
Files included in the current script using an "#include" statement are not analyzed.
WIL function parameter counts ARE checked.
Extenders are not loaded so extender function parameter counts are not checked.
WinBatch function parameter counts are not checked.
WinBatch Compiler:
This release of the WinBatch Compiler also includes the Lexical Analyzer module:
The Compiler's main dialog window contains a new "Analyze source for errors" checkbox.
When this check box is checked, the compiler will use the Lexical Analyzer module to
scan the target script for errors before compilation begins.
If any errors or warnings are found, the Compiler can display a dialog showing a list of
errors and warning. Press this dialog's "Continue" button to proceed with the
compilation or press the "Cancel" button to either return to the main Compiler window or
exit the compiler when the compiler starts with a command line target. In all cases
pressing the "Cancel" button prevents the target from being compiled.
The "Analyze source for errors" checkbox option is global. Once it is checked, syntax
checking is performed on all compiles by the WinBatch+Compiler user until it is
unchecked.
If the "Analyze source for error" option is selected, the compiler is invoked with the
target script as a command line parameter, and the target script's "cmp" file contains
the "silent=1" option; the Compiler generates a text file of any found errors. The
syntax error dialog is not displayed.
The compiler also generates an error file instead of displaying the syntax error dialog
when it is invoked with a "cmplst" file as a command line parameter.
In both instances, the error file name is the target script's file name with a time
stamp and a ".txt" file extension. The file is placed in the target's location on the
file system.
