ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007112Part 01: TTCN-3 Core LanguageNew Featurepublic27-07-2015 11:1911-12-2015 15:23
ReporterJacob Wieland - Spirent 
Assigned ToGyorgy Rethy 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Versionv4.8.1 (published 2016-07)Fixed in Versionv4.8.1 (published 2016-07) 
Clause Reference(s)6.1.1., A.1.6.6.
Source (company - Author)Testing Technologies - Jacob Wieland
Summary0007112: allow different syntax for binary string types
DescriptionIt is very often a hassle to convert a binary representation taken from some other tool into a TTCN-3 octestsring or bitstring.

In normal representations, there are often spaces allowed between groups of digits or there are prefixes like 0x or 0b in front of some digit groups.

It would be very convenient if such a representation could be used directly in TTCN-3 as well so that no conversion would be necessary anymore.

Also, the strings can thus be structured and made more readable. Better readability almost always improves the quality of code.

Minimally, allowing spaces would be sufficient. For convenience sake allowing newlines and 0x/0b prefixes would be a bonus.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filesdocx CR7112_resolution_v1b.docx (34,757) 06-08-2015 15:34
http://oldforge.etsi.org/mantis/file_download.php?file_id=3247&type=bug
docx CR7112_resolution_v2b.docx (35,193) 07-08-2015 12:34
http://oldforge.etsi.org/mantis/file_download.php?file_id=3257&type=bug
Issue History
Date ModifiedUsernameFieldChange
27-07-2015 11:19Jacob Wieland - SpirentNew Issue
03-08-2015 11:07Gyorgy RethyNote Added: 0013023
03-08-2015 11:07Gyorgy RethyAssigned To => Axel Rennoch
03-08-2015 11:07Gyorgy RethyStatusnew => assigned
04-08-2015 09:08Gyorgy RethyProjectTTCN-3 Change Requests => Part 01: TTCN-3 Core Language
06-08-2015 13:05Jacob Wieland - SpirentTarget Version => v4.8.1 (published 2016-07)
06-08-2015 15:34Axel RennochFile Added: CR7112_resolution_v1b.docx
06-08-2015 15:35Axel RennochNote Added: 0013119
06-08-2015 15:36Axel RennochNote Added: 0013120
06-08-2015 15:36Axel RennochAssigned ToAxel Rennoch => Jacob Wieland - Spirent
06-08-2015 15:36Axel RennochStatusassigned => acknowledged
07-08-2015 09:03Jacob Wieland - SpirentNote Added: 0013122
07-08-2015 12:34Axel RennochFile Added: CR7112_resolution_v2b.docx
07-08-2015 12:35Axel RennochNote Added: 0013142
07-08-2015 12:35Axel RennochStatusacknowledged => resolved
07-08-2015 12:35Axel RennochResolutionopen => fixed
07-08-2015 12:35Axel RennochAssigned ToJacob Wieland - Spirent => Gyorgy Rethy
04-11-2015 14:02Gyorgy RethyFixed in Version => v4.8.1 (published 2016-07)
11-12-2015 15:23Gyorgy RethyNote Added: 0013601
11-12-2015 15:23Gyorgy RethyStatusresolved => closed

Notes
(0013023)
Gyorgy Rethy   
03-08-2015 11:07   
STF discussion 03-08-2015: Agreed to allow spaces. Analyse also possible introduction of alternative syntaxes.
(0013119)
Axel Rennoch   
06-08-2015 15:35   
following the discussion the uploaded file considers spaces and newlines, but not 0x/0b prefixes.
(0013120)
Axel Rennoch   
06-08-2015 15:36   
Please check the uploaded proposed solution for correctness.
(0013122)
Jacob Wieland - Spirent   
07-08-2015 09:03   
Small amendment, the newline shall consist of 'any combination of the newline characters that constitute a newline' (i.e. under windows CR LF is just ONE newline). Known combinations (to me) are: CR LF (windows), LF (linux), CR (macos). Maybe this should be reflected in the BNF rule.

NLChar ::= CR [LF] | LF | VT
(0013142)
Axel Rennoch   
07-08-2015 12:35   
final rewording to consider windows newlines (CR LF)
(0013601)
Gyorgy Rethy   
11-12-2015 15:23   
Added to draft V4.7.4