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
  • #386
Closed
Open
Issue created Jan 02, 2017 by Jens Gerlach@gerlach

label Pre in function contracts

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


Id Project Category View Due Date Updated
ID0002265 Frama-C Kernel > ACSL implementation public 2017-01-02 2017-01-02
Reporter jens Assigned To virgile Resolution open
Priority normal Severity minor Reproducibility always
Platform - OS - OS Version -
Product Version Frama-C 14-Silicon Target Version - Fixed in Version -

Description :

I have recently noted that we use both 'Pre' and 'Old' in function contracts of "ACSL by Example". The ACSL description, however, mentions the label 'Pre' only for statement annotations.

Is there a reason to allow both labels in function contracts? If not, then I would suggest to forbid 'Pre' in function contracts.

Attachments

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