ETSI's Bug Tracker - Ext Pack: Object-oriented features (ES 203 790)
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007985Ext Pack: Object-oriented features (ES 203 790)[All Projects] Generalpublic05-10-2020 06:3628-12-2020 10:58
ReporterKristóf Szabados 
Assigned ToJens Grabowski 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product VersionV1.2.1 (published 2020-05) 
Target VersionV1.3.1 (ongoing)Fixed in Version 
Summary0007985: allow objects inside record of/array
DescriptionCurrently Object in TTCN-3 are not allowed as elements of Record of structures.
This creates a limitation in how usable they are.

For example: while it is possible to implement linkedlist like datastructures, it is not possible to implement arraylists, vectors, or open address hashing.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filesdocx CR_7985.docx (135,403) 08-10-2020 08:21
http://oldforge.etsi.org/mantis/file_download.php?file_id=3959&type=bug
docx CR_7985_v2.docx (135,738) 08-10-2020 20:52
http://oldforge.etsi.org/mantis/file_download.php?file_id=3962&type=bug
docx CR_7985_v3.docx (135,772) 09-10-2020 15:10
http://oldforge.etsi.org/mantis/file_download.php?file_id=3963&type=bug
Issue History
Date ModifiedUsernameFieldChange
05-10-2020 06:36Kristóf SzabadosNew Issue
05-10-2020 08:27Jens GrabowskiAssigned To => Kristóf Szabados
05-10-2020 08:27Jens GrabowskiStatusnew => assigned
08-10-2020 08:21Kristóf SzabadosFile Added: CR_7985.docx
08-10-2020 08:21Kristóf SzabadosNote Added: 0015776
08-10-2020 08:22Kristóf SzabadosAssigned ToKristóf Szabados => Jacob Wieland - Spirent
08-10-2020 09:39Jens GrabowskiStatusassigned => confirmed
08-10-2020 16:07Jacob Wieland - SpirentNote Added: 0015786
08-10-2020 16:08Jacob Wieland - SpirentAssigned ToJacob Wieland - Spirent => Kristóf Szabados
08-10-2020 16:08Jacob Wieland - SpirentStatusconfirmed => assigned
08-10-2020 16:09Jacob Wieland - SpirentNote Edited: 0015786bug_revision_view_page.php?bugnote_id=15786#r530
08-10-2020 20:52Kristóf SzabadosFile Added: CR_7985_v2.docx
08-10-2020 20:53Kristóf SzabadosNote Added: 0015787
08-10-2020 20:53Kristóf SzabadosAssigned ToKristóf Szabados => Jacob Wieland - Spirent
08-10-2020 20:53Kristóf SzabadosStatusassigned => confirmed
09-10-2020 15:10Jacob Wieland - SpirentFile Added: CR_7985_v3.docx
09-10-2020 15:12Jacob Wieland - SpirentNote Added: 0015790
09-10-2020 15:12Jacob Wieland - SpirentAssigned ToJacob Wieland - Spirent => Kristóf Szabados
09-10-2020 15:12Jacob Wieland - SpirentStatusconfirmed => assigned
09-10-2020 15:12Jacob Wieland - SpirentStatusassigned => confirmed
16-10-2020 13:04Kristóf SzabadosNote Added: 0015792
16-10-2020 13:04Kristóf SzabadosStatusconfirmed => resolved
16-10-2020 13:04Kristóf SzabadosResolutionopen => fixed
16-10-2020 13:04Kristóf SzabadosAssigned ToKristóf Szabados => Gyorgy Rethy
17-12-2020 16:13Gyorgy RethyAssigned ToGyorgy Rethy => Jens Grabowski
17-12-2020 16:16Gyorgy RethyProduct Version => V1.2.1 (published 2020-05)
17-12-2020 16:16Gyorgy RethyTarget Version => V1.3.1 (ongoing)
28-12-2020 10:58Jens GrabowskiStatusresolved => closed

Notes
(0015776)
Kristóf Szabados   
08-10-2020 08:21   
uploaded first proposal, please check.
(0015786)
Jacob Wieland - Spirent   
08-10-2020 16:07   
(edited on: 08-10-2020 16:09)
What is the purpose of this sentence:
If a structured type contains a field of a class type, this type is not seen as a data type and its values cannot be used for sending and receiving or as an argument to any expression other than the equality/inequality operator.

of course the type can be used for lots of other things. Parameter passing, assignment, field selection, pretty much anything except encoding and passing to another component.

So, I would reformulate it to:
If a structured type contains a field of a class type, this type is not seen as a data type and its values cannot be used for encoding or decoding, sending or receiving and neither used as an actual parameter (or part therof) to a function started on another component.

Maybe this should be formulated as (different) restrictions in a restrictios section.
(0015787)
Kristóf Szabados   
08-10-2020 20:53   
I aggree. Please review.
(0015790)
Jacob Wieland - Spirent   
09-10-2020 15:12   
I have deleted the additional restriction on subtyping structured types that have class type eleements/fields because that is not necessary, as they do not introduce a subtype for the field, just for the container.

Please confirm, and, if ok, please resolve.
(0015792)
Kristóf Szabados   
16-10-2020 13:04   
can be part of the next version of th extension.