Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F frama-c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 171
    • Issues 171
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • pub
  • frama-c
  • Issues
  • #2338
Closed
Open
Issue created Nov 29, 2010 by Jochen Burghardt@burghardt

Suggest to rename user identifiers to avoid name clashes in ..._why.sx files

ID0000632: This issue was created automatically from Mantis Issue 632. Further discussion may take place here.


Id Project Category View Due Date Updated
ID0000632 Frama-C Plug-in > jessie public 2010-11-29 2010-11-29
Reporter Jochen Assigned To cmarche Resolution open
Priority normal Severity feature Reproducibility always
Platform - OS - OS Version -
Product Version Frama-C Boron-20100401 Target Version - Fixed in Version -

Description :

Simplify yields a "!" ("failure") on the attached program, seemingly because f's parameter name "EQ" clashes with the name of the equality predicate used in the preamble of ftest_why.sx. Simplfy has similar problems with a couple of other names, e.g. "AND". (Alt-ergo doesn't have these problems).

I'd like to suggest to catch those "reserved identifiers" by Jessie and to rename them, like this seems to be done already for "result".

It seems pretty dangerous that the "0.0" in g's body is currently translated into an occurrence of the quantified variable representing g's parameter. While the incorrect g is not verifiable right now, it might become so in future - as soon as a property like "double_value(real_constant_0_0e) == real_constant_0_0e" becomes derivable.

Attachments

  • ftest.c
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking