Allow dynlink/eval usage #5
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r-libs-either-toplevel dependency
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2. This set of commits changes the public api to allow using ocaml-jit as a mechanism similar to dynlink (or eval in dynamic languages). Instead of
init_topwe exposejit_loadandjit_lookup_symbol. Additionally I exposeSymbols,AddressandGlobalsin order to be able to pass symbols from external libraries (eventually I'd like to removeGlobal.symbolsand pass them tojit_load, which should also make unloading easier).I also added a simple eval example. It uses quite a bit of OCaml's internal apis (although not much more than ocaml-jit itself). I'm not sure how maintainable it will be between compiler changes, but it should serve as a nice demonstration.