jgrasp handbook

More documents

Recommendations

Info

18.15 GNU Extensions to C and C++ DRAFT, February 18, 2003, Page 98 Most of the GNU C and C++ extensions are supported for CSD generation. Additional extensions are supported if the "Allow GNU Extensions" box is checked in the compiler settings. Function attributes for C are not supported unless "Allow GNU Extensions" is checked because the syntax is too close to that of a K&R style function definition. You can get around this by defining __attribute__ to nothing in the predefined macros. Nested functions are not supported. These can not be distinguished from declarations without identifier context. Our C parser does not distinguish variables from type names, so that header parsing can be avoided. Breaking strings across lines without using backslashes will not be supported. CSD generation adds text at the beginning of lines, so the original string might not be recovered if there were a syntax error that caused the start of the string not be recognized. The backslash at the end of a line applies regardless of syntactic context, so there is no danger of corrupting backslash-continued strings during CSD generation. 18.16 Extended Awk Regular Expressions From the ORO documentation: This is the traditional Awk syntax that is supported: Alternatives separated by | Quantified atoms Atoms Match 0 or more times. + Match 1 or more times. ? Match 0 or 1 times. regular expression within parentheses a . matches everything including newline a ^ is a null token matching the beginning of a string but has no relation to newlines (and is only valid at the beginning of a regex; this differs from traditional awk for the sake of efficiency in Java). a $ is a null token matching the end of a string but has no relation to newlines (and is only valid at the end of a regex; this differs from traditional awk for the sake of efficiency in Java). Character classes (e.g., [abcd]) and ranges (e.g. [a-z]) Special backslashed characters work within a character class Special backslashed characters \b backspace \n newline \r carriage return \t tab \f formfeed
\xnn hexadecimal representation of character \nn or \nnn octal representation of character Any other backslashed character matches itself This is the extended syntax that is supported: • Quantified atoms • Atoms o {n,m} Match at least n but not more than m times. o {n,} Match at least n times. o {n} Match exactly n times. o Special backslashed characters \d digit [0-9] \D non-digit [^0-9] \w word character [0-9a-z_A-Z] \W a non-word character [^0-9a-z_A-Z] \s a whitespace character [ \t\n\r\f] \S a non-whitespace character [^ \t\n\r\f] \cD matches the corresponding control character \0 matches null character 19 Integrated Java Debugger DRAFT, February 18, 2003, Page 99 jGRASP has an integrated debugger for Java. When the debug command is run, if it responds with a transport address (a line like "Listening for transport X at address: Y." ), jGRASP will start the debugger. The default "jdk (integrated debugger) - generic" compiler environment will debug an application or applet with Sun's JDK 1.3. JDK 1.2 with the JPDA for 1.2 might also work, but will probably be quite buggy. To use the integrated debugger, jGRASP must be running under the JDK (not a JRE). If you are having some problem with this (you get a "tools.jar file not on classpath" message when attempting to debug), putting the JDK bin directory at the beginning of the PATH should fix this. For a detailed description of how the jGRASP startup programs find/choose java, see Running jGRASP. Also, you must be running (debugging) your programs under the JDK. The default Java compiler environment uses the classic VM, which is not included in the JRE (you could try copying the compiler environment and modifying it to use HotSpot, but we don't recommend it, as the HotSpot/debugger combination is slow and buggy). If you have the JDK bin directory at the beginning of your PATH and use the default Java compiler environment in jGRASP, there should be no problem. If you can't set things up that way, you will need to copy, modify (add to PATH environment variable), and use a Java compiler environment - see Settings and Compiler Environment Dialog. Do not use the integrated debugger on a dual-processor Windows NT system, as this will most likely lock up jGRASP and the target process, frequently if not always. Using the integrated debugger may lock up jGRASP occasionally. If this happens consistently (every time or every time for some particular target program), or if there are stack dumps from jGRASP, let us know.
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: DRAFT, February 18, 2003, Page 97 s
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 and 120: 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?