Transformation of Applicative Specifications into Imperative ...

More documents

Recommendations

Info

CHAPTER 9. IMPLEMENTATION OF THE TRANSFORMER which recognizes patterns. The actual grammar is placed between the outermost : and ;. The pattern can be a value literal pattern which consists of a value literal, it can be a name pattern which consists of a value name, it can be a record pattern which is of the form name(pattern, ..., pattern), it can be a wild card pattern which consists of an underscore and so on. Example 9.1 – Example of the ANTLR grammar RSL Syntax: pattern ::= value_literal | pure_value_name | record_pattern | wildcard_name | record_pattern ::= pure_value_name(pattern−list) ANTLR grammar: pattern returns [ Pattern p ] { p = null ; Make_ValueOrVariableName vovn = null ; Make_ValueOrVariableName vovn2 = null ; Make_ValueOrVariableName vovn3 = null ; Pattern ip = null ; V a l u e L i t e r a l v l = null ; RSLListDefault i n n e r P a t t e r n L i s t = new RSLListDefault() ; L i s t P a t t e r n lp = null ; } : v l = v a l u e _ l i t e r a l {p = new V a l u e L i t e r a l P a t t e r n ( v l ) ; } | vovn = name {p = new NamePattern ( vovn . value_or_variable_name ( ) . id ( ) , new NoOptionalId ( ) ) ; } | vovn = name LPAREN ip = pattern { i n n e r P a t t e r n L i s t . g e t L i s t ( ) . add ( ip ) ; } ( COMMA ip = pattern { i n n e r P a t t e r n L i s t . g e t L i s t ( ) . add ( ip ) ; } 102
; | | . . . 9.6 The Visitor Modules 9.6. THE VISITOR MODULES ) ∗ RPAREN {p = new RecordPattern ( vovn . value_or_variable_name ( ) , i n n e r P a t t e r n L i s t ) ; } UNDERSCORE { p = new WildcardPattern ( ) ; } The visitors are built using the visitor design pattern. The purpose of the visitor design pattern is to separate a hierarchical structure of classes from tasks which must be performed on the structure itself. When following the visitor design pattern, tasks that would normally be placed in the functionality of the individual class are put inside one single class, called a visitor. When using the visitor design pattern an abstract visitor class is created. This abstract class contains one method, visitClassName, for each class, ClassName, in the hierarchical structure. To each class in the structure a method often called accept or visit is added. This method takes a visitor as argument and calls the visitClassName method. In order to fulfill a task a concrete visitor, which can perform the actual task, is implemented as an implementation of the abstract visitor. Each of the visit methods in the concrete visitor are implemented such that each of them implements a part of the whole task. The advantage of the visitor design pattern is that when a new task is needed, the only thing to do is to make a new concrete visitor. No changes are needed in the classes of the structure. If the functionality of a visitor must be changed, the only class that needs to be changed is the visitor class itself. In the transformer program the RSLAstVisitor.rsl is an abstract visitor and the StringRSLAstVisitor.rsl is a concrete visitor, which can perform the task of turning an RSL AST into an RSL ASCII specification. Part of a class diagram showing the use of the visitor design pattern in the transformer program can be found in Figure 9.6 on the following page. Code snippets of StringRSLAstVisitor.java can be found in Example 9.2. The entire source code of the visitor modules can be found in Appendix F. 103
Page 1:
Transformation of Applicative Speci
Page 5:
Resumé RAISE udviklingsmetoden er
Page 8 and 9:
viii
Page 10 and 11:
CONTENTS 6.4.3 Transforming Value E
Page 12 and 13:
CONTENTS 12.2.4 Interactive Transfo
Page 14 and 15:
xiv
Page 16 and 17:
LIST OF FIGURES xvi
Page 18 and 19:
CHAPTER 1. INTRODUCTION This stepwi
Page 20 and 21:
CHAPTER 1. INTRODUCTION 1. Formulat
Page 22 and 23:
CHAPTER 1. INTRODUCTION 1.7 Content
Page 24 and 25:
CHAPTER 2. GENERAL IDEA end value e
Page 26 and 27:
CHAPTER 2. GENERAL IDEA • In the
Page 28 and 29:
CHAPTER 2. GENERAL IDEA value incre
Page 30 and 31:
CHAPTER 3. TERMINOLOGY Expected Typ
Page 32 and 33:
CHAPTER 3. TERMINOLOGY Example 3.5
Page 34 and 35:
CHAPTER 3. TERMINOLOGY 18
Page 36 and 37:
CHAPTER 4. CONSTRAINTS further deve
Page 38 and 39:
CHAPTER 4. CONSTRAINTS of interest.
Page 40 and 41:
CHAPTER 4. CONSTRAINTS 24
Page 42 and 43:
CHAPTER 5. TRANSFORMABILITY scheme
Page 44 and 45:
CHAPTER 5. TRANSFORMABILITY 28
Page 46 and 47:
CHAPTER 6. TRANSFORMATIONS 6.2.1 Tr
Page 48 and 49:
CHAPTER 6. TRANSFORMATIONS Example
Page 50 and 51:
CHAPTER 6. TRANSFORMATIONS Applicat
Page 52 and 53:
CHAPTER 6. TRANSFORMATIONS object A
Page 54 and 55:
CHAPTER 6. TRANSFORMATIONS type T =
Page 56 and 57:
CHAPTER 6. TRANSFORMATIONS where ge
Page 58 and 59:
CHAPTER 6. TRANSFORMATIONS Ranged s
Page 60 and 61:
CHAPTER 6. TRANSFORMATIONS ✄ end
Page 62 and 63:
CHAPTER 6. TRANSFORMATIONS Value In
Page 64 and 65:
CHAPTER 6. TRANSFORMATIONS ✄ sche
Page 66 and 67:
CHAPTER 6. TRANSFORMATIONS A case e
Page 68 and 69: CHAPTER 6. TRANSFORMATIONS is due t
Page 70 and 71: CHAPTER 6. TRANSFORMATIONS 6.4.4 Tr
Page 72 and 73: CHAPTER 6. TRANSFORMATIONS 56
Page 74 and 75: CHAPTER 7. CORRECTNESS OF TRANSFORM
Page 88 and 89: CHAPTER 8. SPECIFICATIONS The rewri
Page 90 and 91: CHAPTER 8. SPECIFICATIONS RSL speci
Page 92 and 93: CHAPTER 8. SPECIFICATIONS The FUNC
Page 94 and 95: CHAPTER 8. SPECIFICATIONS out, that
Page 96 and 97: CHAPTER 8. SPECIFICATIONS construct
Page 98 and 99: CHAPTER 8. SPECIFICATIONS 8.4.1 Mor
Page 100 and 101: CHAPTER 8. SPECIFICATIONS PRECOND_T
Page 102 and 103: CHAPTER 8. SPECIFICATIONS if length
Page 104 and 105: CHAPTER 8. SPECIFICATIONS subtypes.
Page 106 and 107: CHAPTER 8. SPECIFICATIONS 8.5.2 Cha
Page 108 and 109: CHAPTER 8. SPECIFICATIONS axiom [ m
Page 110 and 111: CHAPTER 8. SPECIFICATIONS Specifica
Page 112 and 113: CHAPTER 8. SPECIFICATIONS the lack
Page 114 and 115: CHAPTER 9. IMPLEMENTATION OF THE TR
Page 126 and 127: CHAPTER 10. EXAMPLES OF TRANSFORMAT
Page 136 and 137: CHAPTER 11. TEST 11.1.1 Lexer and P
Page 138 and 139: CHAPTER 11. TEST An overview of the
Page 140 and 141: CHAPTER 12. POSSIBLE EXTENSIONS OF
Page 146 and 147: CHAPTER 13. CONCLUSION RSL AST and
Page 148 and 149: CHAPTER 13. CONCLUSION 132
Page 150 and 151: BIBLIOGRAPHY [ST02] Donald Sannello
Page 152 and 153: APPENDIX A. USING AND EXTENDING THE
Page 154 and 155: APPENDIX A. USING AND EXTENDING THE
Page 156 and 157: APPENDIX B. CONTENTS OF CD-ROM 140
Page 158 and 159: APPENDIX C. FORMAL SPECIFICATIONS O
Page 168 and 169:
APPENDIX C. FORMAL SPECIFICATIONS O
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
APPENDIX D. SPECIFICATION OF TRANSF
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
Page 412 and 413:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 438 and 439:
Page 440 and 441:
Page 442 and 443:
Page 444 and 445:
Page 446 and 447:
Page 448 and 449:
Page 450 and 451:
Page 452 and 453:
Page 454 and 455:
Page 456 and 457:
Page 458 and 459:
Page 460 and 461:
Page 462 and 463:
Page 464 and 465:
Page 466 and 467:
Page 468 and 469:
Page 470 and 471:
Page 472 and 473:
Page 474 and 475:
Page 476 and 477:
Page 478 and 479:
Page 480 and 481:
Page 482 and 483:
Page 484 and 485:
Page 486 and 487:
Page 488 and 489:
Page 490 and 491:
Page 492 and 493:
APPENDIX E. ANTLR GRAMMAR END = "en
Page 494 and 495:
APPENDIX E. ANTLR GRAMMAR ; d = d e
Page 496 and 497:
APPENDIX E. ANTLR GRAMMAR ; } ( com
Page 498 and 499:
APPENDIX E. ANTLR GRAMMAR ; ) ∗ }
Page 500 and 501:
APPENDIX E. ANTLR GRAMMAR ; } else
Page 502 and 503:
APPENDIX E. ANTLR GRAMMAR prod_bind
Page 504 and 505:
APPENDIX E. ANTLR GRAMMAR ; | | | |
Page 506 and 507:
APPENDIX E. ANTLR GRAMMAR ; | NAT {
Page 508 and 509:
APPENDIX E. ANTLR GRAMMAR ; { ve3 =
Page 510 and 511:
APPENDIX E. ANTLR GRAMMAR ( | RPARE
Page 512 and 513:
APPENDIX E. ANTLR GRAMMAR | { optio
Page 514 and 515:
APPENDIX E. ANTLR GRAMMAR new RSLLi
Page 516 and 517:
APPENDIX E. ANTLR GRAMMAR infix_op_
Page 518 and 519:
APPENDIX E. ANTLR GRAMMAR : v l = v
Page 520 and 521:
APPENDIX E. ANTLR GRAMMAR } t e s t
Page 522 and 523:
APPENDIX E. ANTLR GRAMMAR } : ’ .
Page 524 and 525:
APPENDIX E. ANTLR GRAMMAR 508
Page 526 and 527:
APPENDIX F. SOURCE CODE System . e
Page 528 and 529:
APPENDIX F. SOURCE CODE } } catch (
Page 530 and 531:
APPENDIX F. SOURCE CODE F.2 Visitor
Page 532 and 533:
APPENDIX F. SOURCE CODE public void
Page 534 and 535:
Page 536 and 537:
Page 538 and 539:
Page 540 and 541:
Page 542 and 543:
Page 544 and 545:
Page 546 and 547:
APPENDIX F. SOURCE CODE StringRSLAs
Page 548 and 549:
APPENDIX F. SOURCE CODE } nameOrWil
Page 550 and 551:
APPENDIX F. SOURCE CODE } public vo
Page 552 and 553:
APPENDIX F. SOURCE CODE } r e s u l
Page 554 and 555:
Page 556 and 557:
APPENDIX F. SOURCE CODE } } public
Page 558 and 559:
APPENDIX F. SOURCE CODE } v a l u e
Page 560 and 561:
Page 562 and 563:
Page 564 and 565:
Page 566 and 567:
APPENDIX F. SOURCE CODE } r e s u l
Page 568 and 569:
APPENDIX F. SOURCE CODE } } r e s u
Page 570 and 571:
APPENDIX G. TEST RESULTS continued
Page 572 and 573:
Page 574 and 575:
Page 576:
show all

Transformation of Applicative Specifications into Imperative ...

Create successful ePaper yourself

Delete template?

Save as template?