jgrasp handbook

DRAFT, February 18, 2003, Page 113
Remember to add a path separator when prepending or appending to a path, like "PATH+=C:\newpath;"
on Windows or "PATH+=/usr/local/newpath:" on UNIX/Linux, or
"PATH+=/usr/local/newpath%PATH_SEP" for either.
All variables may be used, so you'll need to escape "%" with "%%". All whitespace is significant, so don't
leave space before the end-of-line or within the command unless you mean it to be there. For example,
"VAR = VALUE" will set "VAR " (VAR followed by a space) to " VALUE" (VALUE preceded by a space).
You can have a plus sign at the beginning of a value by using the %PLUS variable. For example
"VAR=%PLUSval" will set "VAR" to "+val". In most environments, equals signs can not appear in
environment variable names, but for completeness, you can use %EQ to include an equals sign (this will
most likely produce unexpected results).
By default, settings apply to all commands. You can change the commands they apply to using "-
Command" and "+Command" or "Command". For example "-Run" will make the following settings not
apply to the run command, and "+Run" or just "Run" will do the opposite. These commands can be
grouped on a line, separated by whitespace. Use the exact labels in the dialog for command names, only
for Run Applet, use "Run_Applet" (replace space with an underscore).
For example: add C:\mypath to the path but not for run or debug and set DEBUG_TEST to 1 for debug
only.
-Run –Debug
PATH+=C:\mypath;
-Compile -C/L -Check +Debug
DEBUG_TEST=1
23.3.2 Parse Page (C and C++ only)
CSD parsing options for C and C++. These apply only to CSD generation, not to compiling.
Include Path - search path for include files. The directory containing the file is always searched (last).
Include Files - all, none, or only local include files may be parsed. Local includes are defined as those
include by #include "filename" rather than #include . Include file parsing is necessary for CSD
generation if the include files contain unstructured macros (macros that when used, do not look like legal
C or C++ code) or partial code structures. Parsing include files can make CSD generation slow, so it
should be turned off if unnecessary.
Expand Macros - if true, macros are expanded during CSD generation. This may be necessary for
unstructured macros, and for others, some CSD structure for the substitution result may be shown if this
is on.
Use Alternate Tokens - the C++ language allows alternate tokens such as "