ETSI's Bug Tracker - Ext Pack: Object-oriented features (ES 203 790)
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0007985 | Ext Pack: Object-oriented features (ES 203 790) | [All Projects] General | public | 05-10-2020 06:36 | 28-12-2020 10:58

Reporter | KristÃ³f Szabados |
Assigned To | Jens Grabowski |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | V1.2.1 (published 2020-05) |
Target Version | V1.3.1 (ongoing) | Fixed in Version |  |

Summary | 0007985: allow objects inside record of/array
Description | Currently 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 |
Tags | No tags attached.
Relationships |
Attached Files | CR_7985.docx (135,403) 08-10-2020 08:21 http://oldforge.etsi.org/mantis/file_download.php?file_id=3959&type=bug CR_7985_v2.docx (135,738) 08-10-2020 20:52 http://oldforge.etsi.org/mantis/file_download.php?file_id=3962&type=bug 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 Modified | Username | Field | Change
05-10-2020 06:36 | KristÃ³f Szabados | New Issue |
05-10-2020 08:27 | Jens Grabowski | Assigned To | => KristÃ³f Szabados
05-10-2020 08:27 | Jens Grabowski | Status | new => assigned
08-10-2020 08:21 | KristÃ³f Szabados | File Added: CR_7985.docx |
08-10-2020 08:21 | KristÃ³f Szabados | Note Added: 0015776 |
08-10-2020 08:22 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Jacob Wieland - Spirent
08-10-2020 09:39 | Jens Grabowski | Status | assigned => confirmed
08-10-2020 16:07 | Jacob Wieland - Spirent | Note Added: 0015786 |
08-10-2020 16:08 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => KristÃ³f Szabados
08-10-2020 16:08 | Jacob Wieland - Spirent | Status | confirmed => assigned
08-10-2020 16:09 | Jacob Wieland - Spirent | Note Edited: 0015786 | bug_revision_view_page.php?bugnote_id=15786#r530
08-10-2020 20:52 | KristÃ³f Szabados | File Added: CR_7985_v2.docx |
08-10-2020 20:53 | KristÃ³f Szabados | Note Added: 0015787 |
08-10-2020 20:53 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Jacob Wieland - Spirent
08-10-2020 20:53 | KristÃ³f Szabados | Status | assigned => confirmed
09-10-2020 15:10 | Jacob Wieland - Spirent | File Added: CR_7985_v3.docx |
09-10-2020 15:12 | Jacob Wieland - Spirent | Note Added: 0015790 |
09-10-2020 15:12 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => KristÃ³f Szabados
09-10-2020 15:12 | Jacob Wieland - Spirent | Status | confirmed => assigned
09-10-2020 15:12 | Jacob Wieland - Spirent | Status | assigned => confirmed
16-10-2020 13:04 | KristÃ³f Szabados | Note Added: 0015792 |
16-10-2020 13:04 | KristÃ³f Szabados | Status | confirmed => resolved
16-10-2020 13:04 | KristÃ³f Szabados | Resolution | open => fixed
16-10-2020 13:04 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Gyorgy Rethy
17-12-2020 16:13 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Jens Grabowski
17-12-2020 16:16 | Gyorgy Rethy | Product Version | => V1.2.1 (published 2020-05)
17-12-2020 16:16 | Gyorgy Rethy | Target Version | => V1.3.1 (ongoing)
28-12-2020 10:58 | Jens Grabowski | Status | resolved => 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.