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
0008102TTCN-3 Change RequestsTechnicalpublic09-08-2022 15:0126-01-2024 16:32
ReporterMatthias Simon 
Assigned ToMatthias Simon 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Summary0008102: Optional semicolon
DescriptionCurrent semicolon rules are context sensitive and are impossible to be defined properly in grammars without not-predicates/look-ahead (yacc, Bison, ...).

I propose to make the semicolon optional.

Open question: How could we handle conflicts such as:

    alt {
        var integer a[x]
        [y] p.receive
    }
TagsNo tags attached.
Clause Reference(s)A.1.2 -- Statement terminator symbols
For STF discussion
Source (company - Author)Nokia - Matthias Simon
Attached Files

- Relationships

-  Notes
(0016213)
Jens Grabowski (manager)
16-08-2022 09:30

TTF Discussion: Benefits unclear, tools are differently implemented.
(0016288)
Jens Grabowski (manager)
10-11-2022 10:23

Axel, can you have a look?
(0016292)
Axel Rennoch (developer)
10-11-2022 11:01

From the user perspective the semicolon supports readability and avoids unnecessary conflicts or misunderstanding. TTCN-3 is still a specification language and not only for implementation/programming.

In certain cases the semicolon might be avoided and become optional and specified in A.1.2. These explicit cases should be proposed and checked.
(0016297)
Jens Grabowski (manager)
10-11-2022 13:12

TTF discussion: CR cannot be implemented at the moment. TTF agrees that semicolons support readability and understandability of the language.
(0016616)
Olivier Genoud (administrator)
26-01-2024 16:32

In general, we(TF160) like the strict use of semicolons not at least as it may help tools to do automatic indentation. In addition, there seems to be no real benefit from a user's point of view to allow semicolons to be optional.

- Issue History
Date Modified Username Field Change
09-08-2022 15:01 Matthias Simon New Issue
16-08-2022 09:30 Jens Grabowski Note Added: 0016213
16-08-2022 09:31 Jens Grabowski Assigned To => Jens Grabowski
16-08-2022 09:31 Jens Grabowski Status new => assigned
10-11-2022 10:23 Jens Grabowski Note Added: 0016288
10-11-2022 10:23 Jens Grabowski Assigned To Jens Grabowski => Axel Rennoch
10-11-2022 11:01 Axel Rennoch Note Added: 0016292
10-11-2022 11:02 Axel Rennoch Assigned To Axel Rennoch => Matthias Simon
10-11-2022 13:12 Jens Grabowski Note Added: 0016297
10-11-2022 13:13 Jens Grabowski Status assigned => closed
10-11-2022 13:13 Jens Grabowski Resolution open => fixed
26-01-2024 16:32 Olivier Genoud Note Added: 0016616


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