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.

Sign up for GitHub

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

Jump to bottom

Separation between aggregate logic and interpreter #9

Open
metaphori opened this issue Jul 31, 2017 · 0 comments
Open

Separation between aggregate logic and interpreter #9

metaphori opened this issue Jul 31, 2017 · 0 comments
Labels
enhancement minor

Comments

@metaphori
Copy link
Contributor

Originally reported by: Roberto Casadei (Bitbucket: metaphori, GitHub: metaphori)

Currently, the program logic and the interpreter are tightly coupled in the notion of AggregateProgram (all started from the ExecutionTemplate).

The key point seems to pertain to when these two parts (aggregate logic and aggregate computing machinery) needs to be fused.

  • whether statically, and at which point in the hierarchies
  • and/or dynamically, also dealing with usability in API and state management in the VM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement minor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@metaphori