Logo etsi

ETSI's Bug Tracker
Main | My View | View Issues | Change Log | Roadmap | Monitor project
  
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
0007986Part 01: TTCN-3 Core LanguageClarificationpublic07-10-2020 12:4117-12-2020 10:41
ReporterKristóf Szabados 
Assigned ToGyorgy Rethy 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version4.12.1 (published 2020-05) 
Target Version4.13.1 (ongoing)Fixed in Version4.13.1 (ongoing) 
Summary0007986: usage of the "data type" term is a bit confusing
DescriptionSection 3.1 defines the term "data type" as such
"
data types: all types whose values or sub-elements cannot contain object references.
NOTE: Data types include simple basic types, basic string types, and the special data type anytype. Data types also include all structured types where all their sub-elements are of a data type. All user defined types based on a data type are data types as well. See more details in table 3 of the present document.
"

Later section 5.0 states:
"A module consists of a set of definitions that define test components, communication ports, data types, constants, test data templates, functions including the module control function, signatures for procedure calls at ports, test cases, etc. "
This might indicate that is a module can not have a type definition whose sub element can contain an object reference.

And
"TTCN-3 has a number of predefined basic data types as well as structured types such as records, sets, unions, enumerated types and arrays."
But structured types are also data types, or are they explicitly mentioned here to indicate structured types containing object references?

section 6.2.6 states:
"the anytype shall comprise all the known data types but not the port, component, default and timer types"
But types like timers are not data types, so the exclusion makes no difference here.
TagsNo tags attached.
Clause Reference(s)3.1, 5.0, 6.2.
Source (company - Author)L.M. Ericsson
Attached Filesdocx file icon CR7986.docx [^] (1,416,591 bytes) 09-12-2020 16:43

- Relationships

-  Notes
(0015827)
Jens Grabowski (manager)
09-12-2020 16:47

 Tomas, please check. I looked through the cases specified above, changed "address data type" to "address type" and checked all other occurrences of data type.
(0015833)
Tomas Urban (developer)
10-12-2020 07:48

 Looks fine to me. I think it can be added to the next verions of the core language specification.
(0015876)
Gyorgy Rethy (reporter)
17-12-2020 10:41

 Implemented in draft 4.12.2

- Issue History
Date Modified Username Field Change
07-10-2020 12:41 Kristóf Szabados New Issue
08-10-2020 09:37 Jens Grabowski Assigned To => Jens Grabowski
08-10-2020 09:37 Jens Grabowski Status new => assigned
07-12-2020 12:09 Jens Grabowski Project TTCN-3 Change Requests => Part 01: TTCN-3 Core Language
09-12-2020 16:43 Jens Grabowski File Added: CR7986.docx
09-12-2020 16:47 Jens Grabowski Note Added: 0015827
09-12-2020 16:47 Jens Grabowski Assigned To Jens Grabowski => Tomas Urban
10-12-2020 07:48 Tomas Urban Note Added: 0015833
10-12-2020 07:48 Tomas Urban Status assigned => resolved
10-12-2020 07:48 Tomas Urban Resolution open => fixed
10-12-2020 07:48 Tomas Urban Assigned To Tomas Urban => Gyorgy Rethy
17-12-2020 10:41 Gyorgy Rethy Note Added: 0015876
17-12-2020 10:41 Gyorgy Rethy Status resolved => closed
17-12-2020 10:41 Gyorgy Rethy Product Version => 4.12.1 (published 2020-05)
17-12-2020 10:41 Gyorgy Rethy Fixed in Version => 4.13.1 (ongoing)
17-12-2020 10:41 Gyorgy Rethy Target Version => 4.13.1 (ongoing)

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