Pink (my WIP lua ink compiler) support #7
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.
Closes #6
Hi, I see you added 'initial support for incompatible versions', please let me know if I can use it (or if I should make any changes in my PR)
I didn't include the update_site.yml file changes yet (should I?) but in my fork I run it with
python3 proof.py pink_compiler pink_runtime
Another thing I wasn't sure about was that I store my compiled "bytecode" in a new file
*_pink.lua
.I didn't have any file format for it as it's just a lua data structure passed from the compiler to the runtime.
So I serialized it to a lua file so I can easily 'require' (include) it in the runtime script but for that it needed to be called
*.lua
I also found it useful to be able to display it so in my fork I changed the
compileBytecodePath
link. Would it be possible to somehow add the link to the pink.lua file too? (example: https://premek.github.io/ink-proof/#!/file/pink_compiler_I002_out_pink.lua?overview=ink )Let me know what you think
thanks