Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
OcarinaPython
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • TASTE
  • OcarinaPython
  • Issues
  • #1

Closed
Open
Opened May 05, 2017 by Raquel Jalvo Penin @rjpenin

Generation of Context-xxx.c

When there is function with context Parameters in a Interface View, if skeletons are generated, Context-xxx.c and Context-xxx.h are also generated in function folder. If you change the Context Parameters and build the Code (without generating skeletons again), the file Context-xxx.c does not change while that file Context-xxx.c ,generated in binary.c folder, does. I think this situation can mislead to Taste Users. I'd prefer that TASTE advised that the user forgot to generate skeletons or that Context-xxx.c was generated again since that's way there are two different Context-xxx.c.

Thank you very much.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: taste/ocarinapython#1