ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0000567 | Part 01: TTCN-3 Core Language | Technical | public | 19-01-2007 15:07 | 12-03-2008 10:24

Reporter | Pavel Yakovenko |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v3.1.1 (published 2005-06) |
Target Version | v3.3.2 (published 2008-04) | Fixed in Version | v3.3.2 (published 2008-04) |
Clause Reference(s) | 374
Source (company - Author) | Pavel Yakovenko, ISPRAS

Summary | 0000567: Asymetry between sender and recipient addresses in muticast operations

Description

There exists confusing asymmetry between sender and recipient addresses in multicast operations which doesn't allow specifying incompatible component references in multicast receive. Just compare ToClause(0000347) and FromClause(0000374) BNF rules.
When sending data one may use ?(recipient1, recipient2, recipient3)? list of inline templates in multicast send. Since this is not a ?value list? all entries in this list may have different and incompatible types.
For example:
type component CT1 {
port PT P1
}
type component CT2 {
port PT P2
}
function f() {
var CT1 c1 := CT1.create;
var CT2 c2 := CT2.create;
P.send(1) to (c1, c2); //CORRECT, although C1 and C2 are not compatible
}
But when specifying valid senders in multicast receive we have to use ?value list? notation and all entries must have compatible types.
function f() {
var CT1 c1 := CT1.create;
var CT2 c2 := CT2.create;
P.receive(1) from (c1, c2); //ILLEGAL, type error since CT1 and CT2 are incompatible
}
This issue may be resolved by changing BNF rule 0000374 to:
FromClause ::= FromKeyword (AddressRef | AddressRefList | AnyKeyword ComponentKeyword)
In this case "from any component" (or "from ?") has the same meaning as not specifying sender address at all but such notation may be used to make TTCN-3 code more clear to the reader.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR-567-Asymetry-Between-Sender-and-Recipient-Addresses-in-Muticast-Operations-Resolution.doc (1,084,928) 04-12-2007 15:43 http://oldforge.etsi.org/mantis/file_download.php?file_id=1197&type=bug

Issue History
Date Modified | Username | Field | Change
19-01-2007 15:07 | Pavel Yakovenko | New Issue |
19-01-2007 15:07 | Pavel Yakovenko | Clause Reference(s) | => 374
19-01-2007 15:07 | Pavel Yakovenko | Source (company - Author) | => Pavel Yakovenko, ISPRAS
15-06-2007 19:12 | Stephan Schulz | Status | new => assigned
15-06-2007 19:12 | Stephan Schulz | Assigned To | => Ina Schieferdecker
13-10-2007 18:45 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Jens Grabowski
18-10-2007 13:07 | Ina Schieferdecker | Target Version | => Edition 3.3.1 (not yet published)
18-10-2007 13:07 | Ina Schieferdecker | Description Updated |
04-12-2007 15:43 | Jens Grabowski | File Added: CR-567-Asymetry-Between-Sender-and-Recipient-Addresses-in-Muticast-Operations-Resolution.doc |
04-12-2007 15:43 | Jens Grabowski | Assigned To | Jens Grabowski =>
04-12-2007 15:44 | Jens Grabowski | Assigned To | => Thomas DeiÃŸ
04-12-2007 15:44 | Jens Grabowski | Resolution | open => fixed
04-12-2007 17:03 | Thomas DeiÃŸ | Note Added: 0004290 |
04-12-2007 17:03 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Ina Schieferdecker
04-12-2007 17:03 | Thomas DeiÃŸ | Status | assigned => resolved
05-12-2007 17:18 | Ina Schieferdecker | Status | resolved => closed
05-12-2007 17:18 | Ina Schieferdecker | Fixed in Version | => Edition 3.3.1 (not yet published)
12-03-2008 10:22 | user10 | Fixed in Version | Edition 3.3.1 --will not be published, see 3.3.2 => Edition 3.3.2 (not yet published)
12-03-2008 10:24 | user10 | Target Version | Edition 3.3.1 --will not be published, see 3.3.2 => Edition 3.3.2 (not yet published)

Notes

(0004290)
Thomas DeiÃŸ
04-12-2007 17:03

checked by Thomas, ok.