1 # Program Preprocessor {#preprocessor}
3 gclib's program downloader provides a preprocessor for DMC code. The
4 preprocessor modifies the program prior to download providing a number of
5 language features not present in pure DMC code.
7 The preprocessor is invoked in the following two ways.
9 -# With both GProgramDownload() and GProgramDownloadFile() via the
10 `preprocessor` argument. Downloading code with null for the preprocessor
11 argument uses defaults.
12 -# From within DMC code via in-band preprocessor directives.
14 ##The `preprocessor` argument
16 GProgramDownload() and GProgramDownloadFile() can be called with a string passed
17 to the `preprocessor` argument. The program will be modified based on this
18 string prior to download. See *Preprocessor Options* below for syntax.
22 DMC code can be written with special markup to signal the preprocessor to take
23 actions prior to download.
25 For example, the following progam will invoke the in-band preprocessor. The
26 specifics are described below.
29 ## Author: Zaphod Beeblebrox
30 ## Project: Total Perspective Vortex
31 //the above 4 hashmarks enable the preprocessor
32 ##option "--min 4" //use a minimum of level four compression
33 REM REM-style comments are supported at all times
42 Lines beginning with the string `REM` are removed prior to download. `REM`
43 comments are always removed regardless of whether the other preprocessor options
48 Most preprocessor statements begin with a double hash, `##`. When proceeded by
49 a space, the double hash acts like a `REM` comment.
51 When proceeded by a character other than space, `##` is interpreted as a
52 preprocessor directive. For example, see `##option` below.
54 \note Double hash lines are removed from the program only when the
55 preprocessor is enabled with a quad hash.
57 ###Quad Hash to enable
59 In order to enable the in-band preprocessor, the first two lines of the DMC
60 program must start with a double hash. This syntax of using two lines with
61 double hashmarks is called a *quad hash*.
63 Content may follow the hash marks. For example, a good code writing style is to
64 use double hash comments as a comment header showing author, project name, etc.
68 With the preprocessor enabled, C-style comments may be used with the `//` prefix.
69 These comments are very similar to `REM` comments. The primary advantage of
70 using this comment over `REM` is that `//` comments may occur anywhere in a
71 line. This is helpful for line comments such as the following.
74 SIA= 1,25,25,0<4>1 //SSI 25 bits total, all single turn, no status
77 Strings containing `//` are not interpreted as comments.
79 \note `//` comments are removed from the program only when the preprocessor
80 is enabled with a quad hash.
82 ### Preprocessor Directives
84 \note Directives are only followed when the preprocessor is enabled with a
89 The `option` directive allows passing switches directly to the preprocessor with
90 the same syntax as the `preprocessor` argument in GProgramDownload() and
91 GProgramDownloadFile(). The syntax of the `option` directive is the following.
94 ##option "{preprocessor switches}"
97 For example, the following line will disable compression in the program.
103 See *Preprocessor Options* below for other switches.
107 The `include` directive provides a way to include the contents of another DMC
108 file in the current program. This is useful for reusing code such as automatic
109 subroutines, homing operations, or controller initilization routines.
111 The contents of the file will be inserted in place of the `include` line. The
112 insertion occurs prior to code compression.
114 The syntax of the `include` directive is the following.
117 ##include "{path to file}"
123 ##include "c:\galil\initialize.dmc"
129 In addition to gclib,
130 <a href="http://galil.com/downloads/software/gdk">Galil Design Kit</a> supports
131 the preprocessor. Proper preprocessor usage will be colored in the Editor's
132 syntax highlighter. If the quad hash is not present, preprocessor syntax will be
133 colored differently to indicate inproper usage.
135 The preprocessor is not supported in software prior to GDK/gclib. DMC code
136 downloads using the in-band preprocessor in prior generation software (e.g.
137 GalilTools or SmartTerm) will fail.
140 ##Preprocessor Options
142 * Lines beginning with `REM` are always removed from the text prior to download.
143 * A `\` character on a line other than a preprocessor line will result in an error.
144 * Trailing semicolons are removed.
146 ###Compression, `--min`, `--max`
149 * Use maximum compression, only if needed, to fit the program.
150 * `--max` *n* provides preprocessing up to and including level *n*.
151 Only the necessary preprocessing will be performed up to level *n*.
152 * `--min` *n* will preprocess at least up to and including *n*. *n* defined as with `--max` above.
154 ####Compression Levels, *n*
156 * Level 0 (mandatory)
157 -# Comment blank lines with '.
158 -# Remove white space (space/tab) in front of # (label declarations).
159 -# Remove white space after commands.
160 -# Line ends changed to carriage return.
161 -# Replace leading tabs with double space.
162 -# Replace non-leading tabs with single space.
164 -# Remove unnecessary spaces. Strings, comments ('), and no-ops (NO) are not changed.
166 -# Remove comments (') but not no-ops (NO).
168 -# Remove no-ops (NO) too.
170 -# Break apart compound lines that are too long.
171 -# Compact lines of code to maximize line usage.
172 -# Use backtick to support long lines where applicable.
174 ###Code insertion, `--insert`
176 * Code download begins at line zero and overwrites anything present.
177 * `--insert` *arg* invokes the insert option of the firmware's *DL* command. *arg* can be one of the following.
178 -# Line number, e.g. `100`. Program insertion will occur on the line after the line specified.
179 -# Variable name, e.g. `myvar`. Program insertion will occur on the line after the line equal to the value of the variable.
180 -# Label callout, e.g. `#mylabel`. Program insertion will occur on the line after the label.
181 -# A lone `#` symbol. Program insertion will occur on the line after the last line in the program buffer.
182 * Compression directives `--max` and `--min` are followed.
183 * All original code following the point of insertion is cleared.
184 * Not all products support the `--insert` operation, e.g. DMC-30010.
185 See the <a href="http://www.galil.com/download/comref/comall/index.html#download.html">DL</a> command for support.
188 \warning It is the user's responsibility to ensure that the code
189 will fit in the inserted location. The preprocessor will not check line numbers
190 when executing the `--insert` option.
192 ### Include Search Paths, `--search`, `-I`
193 * The `##include` directive will attempt to open its string argument
194 directly. The open will succeed if the argument is the absolute path, or if
195 the argument is in the executable's path, e.g. in the same directory.
196 * `--search` *path* allows the user to specify a directory or directories
197 to be searched for the `include` file in case the first open fails.
198 * `-I` is shorthand for `--search`.
199 * Multiple directories may be specified with multiple `-I` directives.
200 * For in-band code, `-I` must be specified prior to the include.
201 * A common use for `-I` is to specify only the filename in the DMC source code
202 and use the `preprocessor` argument during download to specify the path to the
203 files. This allows the files to be moved without a change to source code.
205 -# The `##include` argument is checked first as-is.
206 -# Then each `-I` argument in the `preprocessor` argument, in the order specified.
207 -# Then `##option` directives in the DMC file, in the order specified.
212 ##option "-I /code/dmc/homing"
213 ##option "-I /code/dmc"
215 //executable's directory will be checked
216 //then c:\code\dmc\homing
220 ### Macro Definition, `--define`, `-D`
221 * `--define` provides a way to substitute one token for another. This
222 is useful for writing code that is generic until program download. Wherever
223 the token is found in code, it is substituted by the replacement. The replacement
224 occurs right before code compression.
225 * `-D` is shorthand for `--define`.
226 * The token should consist of a starting backslash character, followed by upper
227 or lower case alphanumeric characters, underscores, and an ending backslash.
228 * The common usage for this feature is to write code with a token, and then call the
229 program download with the `-D` switch.
231 In this example, an axis is defined at download time. Specifying the
232 following for the preprocessor argument
238 would cause the following code
254 This causes the *A* axis to be addressed.
258 * See the `preprocessor` tag in *editor.xml* to set the desired preprocessor setting
259 for developing in GDK's editor.