Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variables declared VAR should be accessible in a specification #5

Open
csicar opened this issue Mar 25, 2017 · 6 comments
Open

Variables declared VAR should be accessible in a specification #5

csicar opened this issue Mar 25, 2017 · 6 comments

Comments

@csicar
Copy link
Collaborator

csicar commented Mar 25, 2017

Even though they are only "internal" variables, they should be trackable in a specification (for internal testing reasons perhaps) like the counter variable in your example.

I would suggest they are treated similar to OUTPUT variables.

There might be (in a future version) a configuration switch which en/disables the feature.

Commit: 62f6b311b97f394dd3cfc3b0b99bd7aa0deb1c3c

copy of original issue

@csicar csicar added this to the Version 1.3 milestone Jun 8, 2017
@csicar
Copy link
Collaborator Author

csicar commented Jun 22, 2017

VAR could be used as Assumptions and Assertions. At the moment only assertion is used

@csicar
Copy link
Collaborator Author

csicar commented Jun 29, 2017

variables can only be defined at the top-level
these types are possible:

VAR
name: type
VAR_INOUT
name: type

It should be possible to addVar and Var_inout as Input or as Output Variables.

For GeTeTa-Interface:
export Variables as Input or as Output variable, depending on if it is an assumption or an assertion

@csicar csicar added the wip label Jul 5, 2017
@csicar
Copy link
Collaborator Author

csicar commented Jul 6, 2017

in ChangeVariable use Dropdown with Values "INOUT as Input", "INOUT as OUTPUT" etc.

@csicar
Copy link
Collaborator Author

csicar commented Jul 6, 2017

make sure local VAR can be added two times to the spec-table

@csicar
Copy link
Collaborator Author

csicar commented Jul 6, 2017

@csicar
Copy link
Collaborator Author

csicar commented Jul 20, 2017

wrong behaviour when counterexample is avaiable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant