jgrasp handbook

More documents

Recommendations

Info

DRAFT, February 18, 2003, Page 42 As a final example of reading source code with the CSD, consider the following program, which is shown with and without the CSD. FinallyTest illustrates control flow when a break, continue, and return are used within try blocks that each have a finally clause. Although the flow of control may seem somewhat counterintuitive, the CSD should make it easier to interpret this source code correctly. First read the source code without the CSD. Recall that by definition, the finally clause is always executed not matter how the try block is exited. Refer to the output if you need a hint. The output for FinallyTest is as follows: ÏÏfinally 1 ÏÏi 0 ÏÏfinally 2 ÏÏi 1 ÏÏfinally 2 ÏÏfinally 3 Try-Finally with break, continue, and return statements 1 public class FinallyTest { 2 3 public static void main(String[] args) { 4 b: 5 try { 6 break b; 7 } 8 finally { 9 System.out.println("finally 1"); 10 } 11 12 try { 13 for(int i = 0; i < 2; i++) { 14 System.out.println("i " + i); 15 try { 16 if(i == 0) { 17 continue; 18 } 19 if(i < 0) 20 continue; 21 22 return; 23 } 24 finally { 25 System.out.println("finally 2"); 26 } 27 } 28 } 29 finally { 30 System.out.println("finally 3"); 31 } 32 } 33 34 }; 1 ÏÕÖ×public class FinallyTest { 2 ÏÏ§ 3 ÏÏ§ÏÞßàpublic static void main(String[] args) { 4 ÏÏ§ÏÏ§b: 5 ÏÏ§ÏÏ¨¹¹´try { 6 ÏÏ§ÏÏ§Â¹A¹¹Ïbreak b; 7 ÏÏ§ÏÏ§ÏÏ=} 8 ÏÏ§ÏÏ§ÏÏ?finally { 9 ÏÏ§ÏÏ§ÏÏ¨¹¹ÏSystem.out.println("finally 1"); 10 ÏÏ§ÏÏ§ÏÏ©} 11 ÏÏ§ÏÏ§ 12 ÏÏ§ÏÏ¨¹¹´try { 13 ÏÏ§ÏÏ§ÏÏ¨¹¹±for(int i = 0; i < 2; i++) { 14 ÏÏ§ÏÏ§ÏÏ§ÏÏ7¹¹ÏSystem.out.println("i " + i); 15 ÏÏ§ÏÏ§ÏÏ§ÏÏ7¹¹´try { 16 ÏÏ§ÏÏ§ÏÏ§ÏÏ5ÏÏ¨¹³´if(i == 0) { 17 ÏÏ§ÏÏ§ÏÏ§ÏÏÔ¹ÏA¹6¾¹¹Ïcontinue; 18 ÏÏ§ÏÏ§ÏÏ§ÏÏ5ÏÏ=ÏÏ} 19 ÏÏ§ÏÏ§ÏÏ§ÏÏ5ÏÏ>¹³´if(i < 0) 20 ÏÏ§ÏÏ§ÏÏ§ÏÏÔ¹Ï@¹¾¹¹Ïcontinue; 21 ÏÏ§ÏÏ§ÏÏ§ÏÏ5ÏÏ= 22 ÏÏ§Â¹ÄÏÏA¹Ï5ÏÏ@¹¹Ïreturn; 23 ÏÏ§ÏÏ§ÏÏ=ÏÏ5ÏÏ=} 24 ÏÏ§ÏÏ§ÏÏ=ÏÏ5ÏÏ?finally { 25 ÏÏ§ÏÏ§ÏÏ=ÏÏ5ÏÏ¨¹¹ÏSystem.out.println("finally 2"); 26 ÏÏ§ÏÏ§ÏÏ=ÏÏ5ÏÏ©} 27 ÏÏ§ÏÏ§ÏÏ=ÏÏ°} 28 ÏÏ§ÏÏ§ÏÏ=} 29 ÏÏ§ÏÏ§ÏÏ?finally { 30 ÏÏ§ÏÏ§ÏÏ¨¹¹ÏSystem.out.println("finally 3"); 31 ÏÏ§ÏÏ§ÏÏ©} 32 ÏÏ§ÏÏ©} 33 ÏÏ§ 34 ÏÏ©}; In our experience, this code is often misinterpreted when read without the CSD, but understood correctly when read with the CSD.
4 Projects DRAFT, February 18, 2003, Page 43 A project in jGRASP is based on the concept of grouping files together that may be located in on or more directories. When a “project” is created, all information about it is stored in a file with the .gpj extension. If you have not created a project, jGRASP Project: [default] should be displayed at the top of the Desktop, which indicates the general default project file is being used. To use the UML and Object Workbench features of jGRASP, you must organize your Java classes in a Project. UML generation and the Object Workbench (v1.6) are discussed in Section 5. However, projects can be used independently of UML and Object Workbench features. 4.1 Creating a Project On the Control Panel (Desktop) tool bar, click Project – New Project… to open the New Project window (Figure 31). Figure 31. Creating a Project
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: Consider the fragment at right with
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 111 and 112:
Page 113 and 114:
22.5 View Menu DRAFT, February 18,
Page 115 and 116:
• CSD Page • Colors Page • Fo
Page 117 and 118:
Page 119 and 120:
23.2.1.11 View Page DRAFT, February
Page 121 and 122:
Page 123 and 124:
23.4.3 UML Print Settings Page Marg
Page 125 and 126:
File syncing may cause jGRASP to lo
Page 127 and 128:
Page 129 and 130:
flags..............................
show all

jgrasp handbook

Create successful ePaper yourself

Delete template?

Save as template?