Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • T titan.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 45
    • Issues 45
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse Projects
  • Eclipse Titan
  • titan.core
  • Issues
  • #506

Closed
Open
Created Aug 17, 2020 by Eclipse Webmaster@webmasterOwner

Float string representation precision problems

Submitted by G??bor Szalai

Link to original bug (#566118)

Description

The string representation of the TTCN-3 floats are not precise enough. Less significant digits are used than required.

Examples: Code generation problems: TTCN code

var float fl:= 1.0000000000000002 // smallest value greater than 1 representable by 64bit double

Generated C++ code: fl = 1;

Other problematic example: 3.2511111111111113e123

The same precision problem exists in: string2ttcn JSON encoder float2str

The number of the needed significant digits are depends on the used floating point type. In the case of the double at least 17 digits are needed.

Version: 7.1.0

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent