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

Interpreter and intermediate format #24

Open
SpencerPark opened this issue May 13, 2017 · 0 comments
Open

Interpreter and intermediate format #24

SpencerPark opened this issue May 13, 2017 · 0 comments

Comments

@SpencerPark
Copy link
Owner

The compiler has a pseudo intermediate format currently which is just java objects. The compiler generates intermediate code by creating these "Expression" objects which are then executed afterwards. It would make sense to add an intermediate, language agnostic, format that can be interpreted on it's own.

Completely separating an interpreter from the compiler would better support a plugin API and native interface. These things would depend only on the interpreter and could detach from the compiler entirely. Conceptually this is a better place for them anyways.

To get this done there needs to be an explicit, well defined, intermediate standard. Diverging the 2 projects will make implementing new features a bit more extensive but would better encourage backwards compatibility hopefully resulting in a more stable language.

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