| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
It doesn't matter to me if one is using FALSE/TRUE instead of 1/0
but I prefer a type (alias) which emphasizes boolean vars to int.
I changed 1/0 to FALSE/TRUE anyway.
|
|
|
|
|
|
|
|
removing irep array from mrb_state. note that instructions OP_LAMBDA,
OP_EXEC and OP_EPUSH are incompatible, and dumped mrb format has changed.
|
|
|
|
|
|
The length of each string is known. It should be used.
|
|
|
|
This solves the problem of incorrect bytecode generated by mrbc
for single files on Windows platform (which is by default text-mode)
|
|
|
|
|
|
|
|
#1243
|
|
|
|
|
|
|
|
|
|
Show version only once with '-v' option in mruby/mrbc
|
|
|
|
|
|
|
|
|
|
|
|
Added debug infomation section into .mrb file
|
|
|
|
|
|
|
|
It is safer than applying 1bit bit-fields to signed int.
For forward compatibility, you should substiture only 1 or 0 for the variable typed mrb_bool.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|