0007611: Valid port lists for the procedure operations

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

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0007611

Part 01: TTCN-3 Core Language

Clarification

public

13-02-2017 11:27

23-08-2019 09:39

Reporter

Tomas Urban

Assigned To

Gyorgy Rethy

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

v4.9.1 (published 2017-05)

Target Version

v4.10.1 (published 2018-05)

Fixed in Version

v4.10.1 (published 2018-05)

Clause Reference(s)

6.2.9, 22.3

Source (company - Author)

STF 521

Summary

0007611: Valid port lists for the procedure operations

Description

The clause 6.2.9 and related sections of 22.3 don't provide sufficient rules on how signatures listed in the in-list and out-list of port definitions restrict which signatures can be used in procedure-based communication. The used logic is not straightforward, as the in/out directions are assessed from the caller's point of view. Let's demonstrate it on an example with the following definitions:

type signature S() exception (charstring);
port PClient procedure { out S; }
port PServer procedure { in S; }

With these definitions, the following operations using the signature S shall be possible for a port of the PClient type:
- call
- getreply
- catch

And the following operations using the signature S shall be possible for a port of the PServer type:
- getcall
- reply
- raise

There are some hints on how this should work in the core language specification, especially in the way how system adapter works (in 6.2.9, but getcall, reply, raise are not explicitly mentioned) and in the description of the call (22.3.1 restriction a), getcall (22.3.2 restriction b) and raise (22.3.5 restriction b). However, the reply, getreply and catch operations do not contain any relevant restriction and there's no general explanation of the whole logic in 6.2.9.

Proposal:
1. In 6.2.9, explicitly list procedure-based communication operations associated with the in-list and out-list.
2. Extend the list of in and out directions of the system adapter by adding the missing operations.
3. Add the missing restrictions to the reply, getreply and catch operation clauses

Steps To Reproduce

Additional Information

Tags

No tags attached.

Relationships

related to

0007860

closed

Gyorgy Rethy

CR 7611 wasn't properly added to the specification

Attached Files