There are a few things you will need in order to write DCAL macros.

First, you will need the DCAL compiler and linker. If you have a default installation of DataCAD you should have a subdirectory under your main DataCAD directory named DCAL. If you do not have this directory you can install DCAL by running the DataCAD installation program and selecting install DCAL as an option. It is not necessary to install anything else from the DataCAD installation while installing DCAL, so avoid reinstalling the main DataCAD program as this may overwrite your custom settings. Make a note of the directory you install DCAL into.

You will need to add the path to the compiler and linker to your path. The compiler and linker will be located in the directory you specified during the install (typically C:\DATACAD\DCAL.) You should also add the path to your include files. The include files are typically located in a subdirectory of the main DCAL directory named INC (C:\DATACAD\DCAL\INC.) If you do not add the path to your DCAL files to your path you will not be able to compile your source code easily from other directories. You can modify your path by editing your AUTOEXEC.BAT file. In Windows NT you can change the path via the system control panel applet.

You may also create a batch file to modify the path only when needed. Such a batch file might look like:

PATH=%path%;C:\DATACAD\DCAL;C:\DATACAD\DCAL\INC

What this will do is add the path to the compiler, linker and include files to your current path. Modify these paths as needed for your system. By putting this in a batch file you will only have these items in your path when you run the batch files. This is most useful in windows. Adding too many directories to your path can slow down Windows. Simply call this path from a DOS session when you need to work in DCAL. This way when you exit this DOS session the path is reset to the original path.

Next you will need a text editor. This is one area where you will have some freedom. You can use any editor capable of generating unformatted text. Note that you can use your favorite word processor but you should avoid this temptation. The reason not to use a word processor is that it will default to adding formatting when you attempt to save your source code. The compiler will not understand your source code if your editor adds formatting codes such as fonts, margins, etc. You can use notepad or edit which ship with Windows. We recommend getting an editor designed for programming as these tools have powerful functions that can aid you. Check our  DDN Resources page for editors we recommend. Select any editor that you are comfortable using as long as it saves plain, unformatted text files.

The last thing needed is a DOS session. You can use the default DOS window or full screen session but as you build more complex macros you may benefit from increasing the memory available to the DOS session by changing the parameters for the session. Check your windows help files for information on modifying a DOS session.

Once these things are configured you are ready to test your setup.
 

< Previous   |   Continue >

Table of Contents