Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006802Part 01: TTCN-3 Core LanguageClarificationpublic20-10-2014 12:1606-01-2015 18:46
ReporterJacob Wieland - Spirent 
Assigned ToGyorgy Rethy 
PrioritylowSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versionv4.6.1 (published 2014-06) 
Target Versionv4.7.1 (published 2015-06)Fixed in Versionv4.7.1 (published 2015-06) 
Summary0006802: isvalue Definition is inconsistent/confusing
DescriptionIn section C.3.3 (isvalue), it is stated:

"This function is allowed for templates of all data types."

A data type is defined as all types not containing component/port/default on any level.

But, the isvalue function then explicitly is defined as returning true for the null-value which is only valid for component and default types.
TagsNo tags attached.
Clause Reference(s)C.3.3
Source (company - Author)Testing Technologies - Jacob Wieland
Attached Files

- Relationships

-  Notes
(0012368)
Tomas Urban (developer)
20-10-2014 12:39

Null value is valid for the address type too.
(0012369)
Jacob Wieland - Spirent (reporter)
21-10-2014 09:25

You are right, since the address type is also not intrinsically a data type (it is always mentioned additionally to data types) but only additionally allows null explicitly, the same confusion for isvalue arises also for the address type.
(0012370)
Gyorgy Rethy (reporter)
03-11-2014 09:31

I propose the correction:
"C.3.3 The IsValue function
    isvalue(in template any_type inpar) return boolean;

This function is allowed for templates of all data types, <new> component and address types and default values</new>. The function shall ...
The null value assigned to default and component references shall be considered as concrete values."

Note: templates shall not be of default type, that's why this wording.

For ports isvalue would make no sense, they cannot be a value or template at all.
(0012654)
Gyorgy Rethy (reporter)
06-01-2015 18:46

Added to draft V4.6.3

- Issue History
Date Modified Username Field Change
20-10-2014 12:16 Jacob Wieland - Spirent New Issue
20-10-2014 12:39 Tomas Urban Note Added: 0012368
21-10-2014 09:25 Jacob Wieland - Spirent Note Added: 0012369
03-11-2014 09:05 Gyorgy Rethy Project TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
03-11-2014 09:31 Gyorgy Rethy Note Added: 0012370
03-11-2014 09:31 Gyorgy Rethy Product Version => v4.6.1 (published 2014-06)
03-11-2014 09:31 Gyorgy Rethy Target Version => v4.7.1 (published 2015-06)
03-11-2014 15:25 Gyorgy Rethy Status new => resolved
03-11-2014 15:25 Gyorgy Rethy Resolution open => fixed
03-11-2014 15:25 Gyorgy Rethy Fixed in Version => v4.7.1 (published 2015-06)
03-11-2014 15:26 Gyorgy Rethy Assigned To => Gyorgy Rethy
03-11-2014 15:26 Gyorgy Rethy Status resolved => assigned
03-11-2014 15:26 Gyorgy Rethy Status assigned => resolved
06-01-2015 18:46 Gyorgy Rethy Note Added: 0012654
06-01-2015 18:46 Gyorgy Rethy Status resolved => closed


MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker