Custom Query (74 matches)
Results (1 - 3 of 74)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2 | fixed | Add end line information in local dependencies | phdmakk | phdmakk |
| Description |
In addition to the starting line for a definition, it would be nice to also include the ending line for the definition in the local dependencies XML file. |
|||
| #3 | fixed | Add consistency checks during local dependency generation | phdmakk | phdmakk |
| Description |
In connection with #2, there might be some issues with the determination of the exact locations of certain module definitions. These shall be resolved by enforcing certain rules in the implementation of TTCN-3 test code. Subsequently there should be consistency checks that make sure the rules are enforced correctly while generating local dependencies, and if they are not, respective warnings and markers shall be produced to indicate the issues and their causes. The simplest check could be to compare the locations of subsequent definitions, which may as well be sufficient in most scenarios, although its reliability will need to be evaluated. Regarding the output, we could produce a warning and instead of adding arbitrary markers in the line fields, include a distinct element attribute (i.e. "conflict", "warning", etc.) that indicates such issues (it may also provide additional information in this case). |
|||
| #4 | fixed | Incorrect identifier selection in checkTypeDefOrderInGroup | phdmakk | phdmakk |
| Description |
The following example generates an incorrect warning due to taking the wrong identifier into consideration in the last definition. Example: Note that alphabetical order is ok!! group g1{
} Warning: Module_TypesAndValues.ttcn: 13-57: WARNING: Structure of Data: Type definitions <"m4","m1"> within group "g1" are not alphabetically ordered!4.1, checkTypeDefOrderInGroup |
|||
