Running Steps CMD File IDE Review
New Win32 Batch File Debugger, Development Environment and Test Tool
Jun 10, 2008 Guy Lecky-Thompson
One of the most painful parts of programming is debugging. Most languages have complete IDE (integrated development environment) support, with debuggers that allow the programmer to step through programs, look at variables, and otherwise trace the execution of their software.
In batch file programming, this was one area that was sadly lacking. Until now. With Running Steps, Stepping Software have begun to address the situation, offering:
- An editor;
- A complete integrated debugger;
- Analysis of batch files before execution.
The 'old' tricks of the trade, such as using echo commands to print out variable values, and pause commands to temporarily halt execution are now things of the past.
This review article looks at the 3 principle features of Running Steps, to help batch file programmers make up their own minds as to whether they can really do without it.
The Debugger
Certainly the best feature of the whole package is the debugger. This is a welcome relief from tedious trial and error programming. All the features one would expect are present:
- Breakpoints;
- Stepping through code;
- Variable watching;
- Conditional breakpoints;
- etc.
The screen is split into two, with the execution pane at the bottom. This shows the command line view of the batch file, so having a dedicated command line window open at the same time is not necessary. All commands can be stepped into, including the somewhat tricky for command. This is a terrific bonus for any batch file programmer.
The debugging itself can become quite involved, but the help files are good, and there is an outstanding tutorial that will help overcome any initial barriers.
The Editing Environment
Firstly, the editing environment is somewhat basic, when compared with other IDEs for languages such as C/C++ and Java. There is a Project Tree, allowing the programmer to group batch files in a modular fashion within a self-contained Project, but it has been placed on the right hand side, rather than the left, with no way to change this default. This is, however, just a small niggle.
A bigger problem is the lack of syntax highlighting for batch commands. It would have been really useful to offer color coding for reserved words, at the very least, as well as possibly lighting up variables and labels, two of the most tricky elements to track visually in a batch file.
One thing that the editor does offer is on the fly error underlining, part of the file analysis process.
File Analysis
Rather than compiling files (since they are command line files), Running Steps provides the possibility to analyze the batch files in the project. It then reports any errors that are found, and offers warnings for other possible inconsistencies.
While it is correct in it's analysis, there is no double-click help available to cross-check the syntax. This means that the programmer must rely on the Windows Help Files, which are notoriously illogical and difficult to navigate when it comes to looking up command line programming topics.
Getting Running Steps
A trial version can be downloaded from the Running Steps website. Be aware, however, that although all errors found using the Analyze tool are listed details for some are only available in the registered version. After 30 days, the trial will also, apparently, cease to function.
However, 30 days ought to give anyone enough time to evaluate the product, and if they create batch programs on a regular basis, it will prove to be a very useful tool to have in one's arsenal.
Running Steps is fantastically easy to use, has a great tutorial, a very powerful integrated debugger, and makes batch file debugging as easy as in any other professional IDE.
Running Steps
|
What do you think about this article?
More in Technology
Latest Articles