| Age | Commit message (Collapse) | Author |
|
from 'mrb_int' to 'int', possible loss of data
|
|
|
|
|
|
|
|
|
|
|
|
The fix was proposed by @block8437. Thank you.
|
|
|
|
|
|
mrb_funcall(); close #3056
|
|
Fiber.yield cannot be called from #initialize which is called by
mrb_funcall(). It is mruby limitation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#2439
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
use the function; there's no function available to create new fiber from C (countapart of Lua's lua_newthread), but that's because you cannot create a new fiber from C due to mruby C API design limitation. define your method to create fibers in Ruby; close #1269
|
|
|
|
|
|
|
|
|
|
|
|
API changes:
- value.p must be accessed via mrb_value_p macro
- value.p must be mutated via MRB_SET_VALUE_P macro
|
|
|
|
|
|
|
|
|