ETSI's Bug Tracker - Part 01: TTCN-3 Core Language |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0003955 | Part 01: TTCN-3 Core Language | Editorial | public | 13-08-2008 22:49 | 12-12-2008 10:49 |
|
Reporter | Claude Desroches | |
Assigned To | Ina Schieferdecker | |
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | | OS Version | |
Product Version | v3.3.2 (published 2008-04) | |
Target Version | v4.1.1 (published 2009-06) | Fixed in Version | v4.1.1 (published 2009-06) | |
Clause Reference(s) | Page 22, section 5.4 |
Source (company - Author) | BluKaktus - Claude Desroches |
|
Summary | 0003955: Text ""TTCN-3 supports value, template, timer and port parameterization†is misleading |
Description | "TTCN-3 supports value, template, timer and port parameterizationâ€
This sentence seems to imply that the elements "value, template, timer, and port" may be parameterized.
However, what is actually meant is that these ‘elements’ can be used as actual/formal parameters to the elements identified in table 2.
This sentence should be changed so that the meaning is clear.
Otherwise one might be led to believe that there is a contradiction between the above sentence, and the NOTE in table 2, which states that port definitions do not allow parameterization.
|
Steps To Reproduce | |
Additional Information | Suggested correction:
Values, templates, timers, and ports may be used as actual and/or formal parameters where permitted by TTCN-3.
|
Tags | No tags attached. |
Relationships | related to | 0002590 | closed | Ina Schieferdecker | parameterization of signatures | related to | 0000403 | closed | Gyorgy Rethy | Port type parameterisation of component types |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
13-08-2008 22:49 | Claude Desroches | New Issue | |
13-08-2008 22:49 | Claude Desroches | Status | new => assigned |
13-08-2008 22:49 | Claude Desroches | Assigned To | => Ina Schieferdecker |
13-08-2008 22:49 | Claude Desroches | Clause Reference(s) | => Page 22, section 5.4 |
13-08-2008 22:49 | Claude Desroches | Source (company - Author) | => BluKaktus - Claude Desroches |
14-08-2008 14:02 | Ina Schieferdecker | Note Added: 0006531 | |
14-08-2008 14:04 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Thomas Deiß |
14-08-2008 14:04 | Ina Schieferdecker | Resolution | open => fixed |
14-08-2008 14:04 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published) |
14-08-2008 14:22 | Thomas Deiß | Note Added: 0006533 | |
09-12-2008 10:24 | Ina Schieferdecker | Relationship added | related to 0002590 |
09-12-2008 10:24 | Ina Schieferdecker | Relationship added | related to 0000403 |
09-12-2008 10:27 | Ina Schieferdecker | Note Added: 0007589 | |
12-12-2008 09:53 | Thomas Deiß | Note Added: 0007676 | |
12-12-2008 09:53 | Thomas Deiß | Assigned To | Thomas Deiß => Ina Schieferdecker |
12-12-2008 10:49 | Ina Schieferdecker | Status | assigned => resolved |
12-12-2008 10:49 | Ina Schieferdecker | Fixed in Version | => Edition 4.1.1 (not yet published) |
12-12-2008 10:49 | Ina Schieferdecker | Status | resolved => closed |
Notes |
|
|
To be changed to "TTCN-3 allows to parameterize modules, types, templates, functions, altsteps and testcases. Values, templates, timers, and ports may be used as actual parameters. A summary of which language elements can be parameterized and what can be passed to them as parameters is given in table 2."
The CR has relations to CR2590 - see there. |
|
|
|
The proposed text in the previous note is fine for me.
I suggest to wait with closing the CR until CR403 on port type parameterization has been resolved. Depending on the resolution of CR403, the proposed text might have to be changed. |
|
|
|
According to resolution of CR403 to be changed to
"TTCN-3 allows to parameterize modules, templates, functions, altsteps and testcases. Values, templates, timers, and ports may be used as actual parameters. A summary of which language elements can be parameterized and what can be passed to them as parameters is given in table 2.
NOTE: Type parameterization for TTCN-3 is defined in the optional package [xx]." |
|
|
|
proposed solution (in note 7589) is ok.
|
|