Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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 61
    • Issues 61
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • 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
  • #304

Closed
Open
Created Jul 24, 2017 by Eclipse Webmaster@webmasterOwner

Re-thought const handling

Submitted by Kristof Szabados

Link to original bug (#520094)

Description

In the current (internal) version of the compiler we are experimenting with letting constant being initialized by module parameters.

But as this has some side-effect we need to run a deeper investigation on it. For example this also becomes possible (although it might not be wished) " function f() return integer { if (rnd() < 0.5) { return 5; } else { return 10; } }

const integer c_dimension := f();
type integer Arr[c_dimension];

"

Version: 6.2.0

Assignee
Assign to
Time tracking

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