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

Method call on this in the context of causality analysis #3

Open
ptal opened this issue Jul 15, 2018 · 0 comments
Open

Method call on this in the context of causality analysis #3

ptal opened this issue Jul 15, 2018 · 0 comments

Comments

@ptal
Copy link
Owner

ptal commented Jul 15, 2018

A problem occurs with method calls such as this.m() since m has accessed to every field of this (see #2).
To allow non-static methods in a spacetime module, we can etiher:

  1. Analyse the Java method to check for read and write accesses (seems very complex since we must parse and understand the full Java syntax).
  2. Annotate the call on this with the permissions of the variables accessed.
  3. Allow possible causality holes when calling external functions (i.e. Java methods).
ptal added a commit that referenced this issue Jul 16, 2018
…. Distinguish between spacetime variables and class names on method calls.
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