Update documentation for mrb_top_run()
#6256
Merged
Conversation
This file contains 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
Also, add explanations for the `mrb_load_irep()` and `mrb_load_string()` families, which are indirect calls to `mrb_top_run()`.
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.
Also, add explanations for the
mrb_load_irep()andmrb_load_string()families, which are indirect calls tomrb_top_run().I added a new feature to my mruby-gemcut and it took me a while to figure out the cause crash.
I need to call
mrb_top_run()indirectly from inside the method, so usingmrb_proc_new_cfunc()andmrb_yield_with_class()as workarounds.Gemcut.facetmethodI was concerned about compatibility if I changed the behavior from within the mruby VM, so I added a note to the documentation first.
I can't think of a better way at this time.