Browse Prior Art Database

A Tool to Simplify DOS Command Line Development Disclosure Number: IPCOM000016530D
Original Publication Date: 2003-Jun-27
Included in the Prior Art Database: 2003-Jun-27
Document File: 2 page(s) / 43K

Publishing Venue



A Utility to Simplify Software Development In a DOS Command Line Environment

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

A Tool to Simplify DOS Command Line Development

   Software development is often done in "DOS command line" environments. All operations performed in these environments are typed at the command line. The source code is quite often in a directory tree with many subdirectories and the project is "built" from one directory which is often the topmost directory. If the developer has to edit a file in one of the subdirectories, it is neccessary to type in the entire path to the file to edit it. It is difficult to remember the complete path to each file (perfectly) and even if the path is known, it can be tedious to type in an entire path. Typing a path strictly from memory introduces the possibility of "file not found" errors or editing the wrong file. There are "file find" utilities that can find a file in a directory tree and display it's location but the developer still has to either type in the path to the file or use "cut and paste" operations to specify a path to the file.

     This can be addressed by creating a DOS command line program (utility) that can find any specified file in a given directory tree and execute any command with the file's complete path and name as a parameter. The utility should also provide a mechanism to specify parameters for the command in addition to the file path and name. It should also be able to search multiple paths that are separated by semi-colons (a multi-path) pre-defined in an environmental variable (i.e., NT's PATH environmental variable).

     Using this utility, a developer working with files that are deep in a directory tree or in a multi-path would not need to specify anything more than the file's name to find it and pass it to another program (i.e., a text editor) or command. This would make it possible to work from the directory where the build command is executed and still have quick, easy access to any files in any directory tree or multi-path.

     This utility takes command line parameters that specify the name of the file for which it will search, the name of a command that it will execute and any additional parameters for the command. If the file name parameter contains path information in addition to a file specification then the path information specifies a search s...