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
0005367SIP LibraryBug reportpublic23-09-2009 18:5302-10-2009 13:41
ReporterAnthony Baire 
Assigned ToStephan Schulz 
PrioritynormalSeveritymajorReproducibilityalways
StatusassignedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0005367: the SIP library contains constructs that are not valid TTCN-3 code
Description
The SIP library contains some code that is not valid TTCN-3 code, consequently it cannot to compile with any strictly conformant TTCN-3 compiler.


1. Standard TTCN-3 does not allow accessing individual fields in templates of structured types. The following lines cannot be compiled:

LibSip_Step.ttcn:1699: loc_media.media_field.transport
LibSip_Step.ttcn:1670: loc_media.media_field.fmts
LibSip_Step.ttcn:2810: p_request.msgHeader.route
LibSip_Step.ttcn:2823: p_request.msgHeader.route
LibSip_Step.ttcn:2824: p_request.msgHeader.recordRoute
LibSip_Step.ttcn:2963: p_response.msgHeader.route
LibSip_Step.ttcn:2964: p_response.msgHeader.recordRoute
LibSip_Templates.ttcn:742: p_hostport.host & p_hostport.portField
LibSip_Templates.ttcn:1729: p_statusLine.statusCode
LibSip_Templates.ttcn:2008: p_statusLine.statusCode
LibSip_Templates.ttcn:2038: p_statusLine.statusCode
LibSip_Templates.ttcn:2048: p_statusLine.statusCode
LibSip_Templates.ttcn:2059: p_statusLine.statusCode
LibSip_Templates.ttcn:2059: p_statusLine.statusCode
LibSip_Templates.ttcn:2069: p_statusLine.statusCode
LibSip_Templates.ttcn:2079: p_statusLine.statusCode
LibSip_Templates.ttcn:2089: p_statusLine.statusCode
LibSip_Templates.ttcn:2103: p_statusLine.statusCode
LibSip_Templates.ttcn:2116: p_statusLine.statusCode
LibSip_Templates.ttcn:2129: p_statusLine.statusCode
LibSip_Templates.ttcn:2141: p_statusLine.statusCode
LibSip_Templates.ttcn:2161: p_statusLine.statusCode
LibSip_Templates.ttcn:2171: p_statusLine.statusCode


2. Standard TTCN-3 does not allow templates in the parameter list of a superset() match (it only allows constant expressions)

LibSipTemplates.ttcn:780: superset(complement(c_tag100rel))
LibSipTemplates.ttcn:848: superset({p_urn, omit})

TagsNo tags attached.
Attached Files

- Relationships
related to 0005154assignedBostjan Pintar Combination of complement and superset cause error 

-  Notes
(0009026)
Stephan Schulz (reporter)
28-09-2009 15:59

I am not sure if you are correct on your first point.
Have you checked Section '15.6 Referencing elements of templates or template fields' ?

Regarding the second issue. That is clearly against the standard and should be removed/changed. I see another issue seems to have been filed on this topic by Bostjan.

We fill try to fix the latter issue in lannion
(0009035)
Anthony Baire (reporter)
02-10-2009 13:41

I went in depth into the first point and now I think that it is a inconsistency in the TTCN-3 language specification.

Section 15.6 states that template fields can be referenced but the BNF in Annex A does not allow such constructs.

Strictly speaking it is not a valid TTCN-3 code because section 4.2 states that in case of contradiction the BNF has precendence over the textual description. ;-)


Anyway I've just opened a change request about this issue: http://t-ort.etsi.org/view.php?id=5375 [^] let's see what happens

- Issue History
Date Modified Username Field Change
23-09-2009 18:53 Anthony Baire New Issue
23-09-2009 18:53 Anthony Baire Status new => assigned
23-09-2009 18:53 Anthony Baire Assigned To => Stephan Schulz
28-09-2009 15:59 Stephan Schulz Note Added: 0009026
28-09-2009 16:00 Stephan Schulz Relationship added related to 0005154
02-10-2009 13:41 Anthony Baire Note Added: 0009035


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