ETSI's Bug Tracker |
Anonymous | Login | Signup for local Mantis account | 17-05-2024 10:38 IST |
Main | My View | View Issues | Change Log | Roadmap | Monitor project |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0006780 | Part 01: TTCN-3 Core Language | Technical | public | 18-06-2014 15:39 | 20-06-2014 11:45 | ||||
Reporter | Tomas Urban | ||||||||
Assigned To | |||||||||
Priority | normal | Severity | minor | Reproducibility | N/A | ||||
Status | closed | Resolution | won't fix | ||||||
Platform | OS | OS Version | |||||||
Product Version | v4.6.1 (published 2014-06) | ||||||||
Target Version | v4.7.1 (published 2015-06) | Fixed in Version | |||||||
Summary | 0006780: Sender clause should implicitly define the content of the missing from clause | ||||||||
Description | If a receiving statement contains a sender clause, but the from clause is missing, the from clause should be defined from the sender clause implicitly in the following way: var address v_addr; p.receive -> sender v_addr; is equal to p.receive from address:? -> sender v_addr; This way the language rule prevents unnecessary crashes of the testing code caused by incompatibility of the actual sender and the variable used for storing it. A mismatch will be detected instead, which is a situation that can be gracefully handled by the TE. Notice that the described situation is not possible with values as the value clause can be present only when the matching template is defined. Similar solution would be possible for the sender clause (i.e. to bind the sender clause to a presence of the from clause), but such a change wouldn't be backwards compatible. | ||||||||
Tags | No tags attached. | ||||||||
Clause Reference(s) | 22.2.2 | ||||||||
Source (company - Author) | STF 478 | ||||||||
Attached Files | |||||||||
Relationships | ||||||
|
Notes | |
(0012150) Gyorgy Rethy (reporter) 19-06-2014 15:20 |
STF discussion: do not make this addition: this addition could cause DTE when the given branch is not successful and would be a backward incompatible change. |
(0012173) Tomas Urban (developer) 20-06-2014 08:56 |
As the decision of the STF is to reject the CR, the issue is closed as "won't fix". |
Issue History | |||
Date Modified | Username | Field | Change |
18-06-2014 15:39 | Tomas Urban | New Issue | |
18-06-2014 15:52 | Tomas Urban | Relationship added | related to 0006781 |
19-06-2014 15:20 | Gyorgy Rethy | Note Added: 0012150 | |
20-06-2014 08:56 | Tomas Urban | Note Added: 0012173 | |
20-06-2014 08:56 | Tomas Urban | Status | new => closed |
20-06-2014 08:56 | Tomas Urban | Resolution | open => won't fix |
20-06-2014 11:44 | Gyorgy Rethy | Project | TTCN-3 Change Requests => Part 01: TTCN-3 Core Language |
20-06-2014 11:45 | Gyorgy Rethy | Product Version | => v4.6.1 (published 2014-06) |
20-06-2014 11:45 | Gyorgy Rethy | Target Version | => v4.7.1 (published 2015-06) |
MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |