jgrasp handbook

More documents

Recommendations

Info

DRAFT, February 18, 2003, Page 112 CSD window, and the icon will not appear on the toolbar. If a run command is empty, that command will not appear on the "Run" menu of the CSD Window, and the icon will not appear on the toolbar. A variety of execution-time variables may be applied to commands and directories. Also, two static variables, %V1 and %V2, can be specified at the bottom of the page. Environment variables can also be modified. Whitespace separates arguments in commands. Use double quotes to specify an argument containing whitespace. Use %' (percent-single quote) to include a double quote in a quoted argument. Any variable can also be used in a quoted argument, and %% (percent-percent) must be used to include a percent symbol. "Command" specifies the command. All variables may be used. "Directory" specifies the working directory for the command. If left blank, the directory containing the file will be used. %PATH, %base, and for Java, %PACKAGE_PATH variables may be used here. "Error Format" specifies the error format for the command. The format string begins with a list of target flags, followed by a dash. The rest of the string is a Perl5 regular expression. See the perlre man page for a description of this format. The target flags are: f = filename c = class 1 = start line 2 = start column 3 = end line 4 = end column For click-to-error to work, the numbers of target flags must be equal to the number of matching groups in the regular expression. If a filename or class is matched and the corresponding file exists, a click will open the file. If the start line is matched, that line will be highlighted. If the start and end lines and columns are matched, that piece of text will be matched. If a filename and class are matched, the filename will be tried first. If the same target type matches multiple times, the last match is used. Unmatched groups are ignored, so you can use or'ed expressions and repeated target flags to match multiple possible formats. No error message is reported if the format is bad, or the number of target flags does not match the number of groups. On the control panel "Tools" menu, there is a testing tool for pattern matches. As an example, "f1-(\S(?:\s*\S)*):(\d+):.*" will match the file and line number of a GNU-style error message. The regular expression reads as: a matching group containing (a non-whitespace character followed by any number of non-matching groups consisting of any number of whitespace characters followed by one non-whitespace character); followed by a colon; followed by a matching group consisting of one or more digits; followed by a colon; followed by anything. In other words, "filename:line_number:other_text", where filename must begin and end with non-whitespace characters and be at least one character long, and line_number consists of one or more digits. "Environment" allows environment variables to be changed. Variables are set one-per-line, using the following format: Replace: VAR=VALUE Prepend: VAR+=VALUE Append: VAR=+VALUE
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 "
Page 1 and 2:
The Table of Contents Index Handboo
Page 3 and 4:
DRAFT, February 18, 2003, Page ii 4
Page 5 and 6:
DRAFT, February 18, 2003, Page iv 1
Page 7 and 8:
DRAFT, February 18, 2003, Page vi 2
Page 9 and 10:
Overview of jGRASP DRAFT, February
Page 11 and 12:
DRAFT, February 18, 2003, Page 3 sp
Page 13 and 14:
DRAFT, February 18, 2003, Page 5 Pr
Page 15 and 16:
DRAFT, February 18, 2003, Page 7 Co
Page 17 and 18:
11 Control Structure Diagram (CSD)
Page 19 and 20:
1 Installing jGRASP DRAFT, February
Page 21 and 22:
2.1 Creating a New File DRAFT, Febr
Page 23 and 24:
In the upper right corner of the CS
Page 25 and 26:
2.2 Saving a File DRAFT, February 1
Page 27 and 28:
2.4 Loading a File DRAFT, February
Page 29 and 30:
DRAFT, February 18, 2003, Page 21 4
Page 31 and 32:
DRAFT, February 18, 2003, Page 23 O
Page 33 and 34:
2.7 Line Numbers DRAFT, February 18
Page 35 and 36:
DRAFT, February 18, 2003, Page 27 T
Page 37 and 38:
2.9 Running a Program DRAFT, Februa
Page 39 and 40:
3 The Control Structure Diagram (CS
Page 41 and 42:
DRAFT, February 18, 2003, Page 33 n
Page 43 and 44:
Selection (cont’d) switch (when b
Page 45 and 46:
3.4 CSD Templates DRAFT, February 1
Page 47 and 48:
3.6 Reading Source Code with the CS
Page 49 and 50:
Consider the fragment at right with
Page 51 and 52:
4 Projects DRAFT, February 18, 2003
Page 53 and 54:
4.2 Adding files to the Project DRA
Page 55 and 56:
4.4 Generating Documentation for th
Page 57 and 58:
4.5 Jar file Creation and Extractio
Page 59 and 60:
DRAFT, February 18, 2003, Page 51 I
Page 61 and 62:
DRAFT, February 18, 2003, Page 53 j
Page 63 and 64:
DRAFT, February 18, 2003, Page 55 M
Page 65 and 66:
DRAFT, February 18, 2003, Page 57 a
Page 67 and 68:
5.5 Displaying Dependencies Between
Page 69 and 70: 5.8 Saving the UML Layout DRAFT, Fe
Page 71 and 72: DRAFT, February 18, 2003, Page 63 b
Page 73 and 74: DRAFT, February 18, 2003, Page 65 t
Page 75 and 76: DRAFT, February 18, 2003, Page 67 V
Page 77 and 78: DRAFT, February 18, 2003, Page 69 T
Page 79 and 80: Part 2 - Reference DRAFT, February
Page 81 and 82: DRAFT, February 18, 2003, Page 73 i
Page 83 and 84: 9.4 Requirements for the Integrated
Page 85 and 86: 13 Known Bugs DRAFT, February 18, 2
Page 87 and 88: Unicode support - this will require
Page 89 and 90: Section 3. Disclaimer of Warranty D
Page 91 and 92: * . * DRAFT, February 18, 2003, Pag
Page 93 and 94: DRAFT, February 18, 2003, Page 85 A
Page 95 and 96: DRAFT, February 18, 2003, Page 87 S
Page 97 and 98: 17.13 Projects DRAFT, February 18,
Page 99 and 100: 17.18 Jar/Zip Extractor Dialog DRAF
Page 101 and 102: DRAFT, February 18, 2003, Page 93 e
Page 103 and 104: 18.8 Find Dialog / Page DRAFT, Febr
Page 105 and 106: DRAFT, February 18, 2003, Page 97 s
Page 107 and 108: \xnn hexadecimal representation of
Page 109 and 110: DRAFT, February 18, 2003, Page 101
Page 113 and 114: 22.5 View Menu DRAFT, February 18,
Page 115 and 116: • CSD Page • Colors Page • Fo
Page 119: 23.2.1.11 View Page DRAFT, February
Page 123 and 124: 23.4.3 UML Print Settings Page Marg
Page 125 and 126: File syncing may cause jGRASP to lo
Page 129 and 130: flags..............................
show all

jgrasp handbook

Create successful ePaper yourself

Delete template?

Save as template?