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

ID | Project | Category | View Status | Date Submitted | Last Update
0007920 | Ext Pack: Object-oriented features (ES 203 790) | [All Projects] General | public | 09-04-2020 09:12 | 28-12-2020 11:09

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 | 0007920: Clarification request: how should equality/inequality work for objects?

Description

According to the currently available version of the OO extension (v1.1.1) the equality/inequality operators can be used with object instances, but only to check if they are null or not.
"An object variable or parameter may be compared with the special value null with the equality and inequality operators or can be assigned the special value null explicitly."
It would be benefitial if objects could be compared.
Also it should be done by their references to see if two object instances are actually the same.
But comparing based on members (like done for record/set and other types) should not work for objects. Since objects of very different types might have the same member fields and function names, but very different operational semantics described within those functions.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7920.docx (131,696) 11-08-2020 10:10 http://oldforge.etsi.org/mantis/file_download.php?file_id=3904&type=bug

Issue History
Date Modified | Username | Field | Change
09-04-2020 09:12 | KristÃ³f Szabados | New Issue |
14-04-2020 12:31 | KristÃ³f Szabados | Summary | Clarification request: who should equality/inequality work for objects? => Clarification request: how should equality/inequality work for objects?
28-05-2020 09:12 | Jacob Wieland - Spirent | Note Added: 0015656 |
10-08-2020 10:26 | Jens Grabowski | Assigned To | => Jacob Wieland - Spirent
10-08-2020 10:26 | Jens Grabowski | Status | new => assigned
11-08-2020 10:10 | Jacob Wieland - Spirent | File Added: CR7920.docx |
11-08-2020 10:11 | Jacob Wieland - Spirent | Note Added: 0015676 |
11-08-2020 10:11 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Tomas Urban
11-08-2020 10:11 | Jacob Wieland - Spirent | Status | assigned => confirmed
11-08-2020 15:27 | KristÃ³f Szabados | Note Added: 0015696 |
13-08-2020 08:51 | Tomas Urban | Note Added: 0015720 |
13-08-2020 08:51 | Tomas Urban | Status | confirmed => resolved
13-08-2020 08:51 | Tomas Urban | Resolution | open => fixed
13-08-2020 08:51 | Tomas Urban | Assigned To | Tomas Urban => Jens Grabowski
17-12-2020 16:22 | Gyorgy Rethy | Product Version | => V1.2.1 (published 2020-05)
17-12-2020 16:22 | Gyorgy Rethy | Target Version | => V1.3.1 (ongoing)
28-12-2020 11:09 | Jens Grabowski | Status | resolved => closed

Notes

(0015656)
Jacob Wieland - Spirent
28-05-2020 09:12

Of course, the intention was that object can be compared via comparing their instances as is usual in object-oriented languages. If that is not yet in the standard, that needs to be added.

(0015676)
Jacob Wieland - Spirent
11-08-2020 10:11

added section on comparison operators in the objects section, please review

(0015696)
KristÃ³f Szabados
11-08-2020 15:27

looks good for me.

(0015720)
Tomas Urban
13-08-2020 08:51

The proposed solution fixes the issue described in this CR and can be added to the next version of the standard.