| Age | Commit message (Collapse) | Author |
|
|
|
removing irep array from mrb_state. note that instructions OP_LAMBDA,
OP_EXEC and OP_EPUSH are incompatible, and dumped mrb format has changed.
|
|
|
|
currently there are two scnenario to call mrb_run(), the first is
calling a proc, in this case mrb should create a new environment,
discarding all the variables except args, reciever and block.
the second is calling the newly generated irep, like in mirb.
in this case, the variables should be kept after mrb_run().
so we introduce mrb_context_run() to handle this seperately.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
separate out `incremental_gc_step()` from `mrb_incremental_gc()`, and misc minor rename
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
remove the redundant codes with mrb_malloc_simple()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
identifier in mruby
|
|
|
|
|
|
is possible to conflict an application's macro.
|
|
|
|
crimsonwoods-suppress_intern
|
|
|
|
at once
|
|
|
|
|
|
|
|
|
|
|