What happened this week on the mruby front?
After a request of Masaki Muranaka the non-functional code of eval was removed from mruby. Herewith it should be clear that this kind of feature won’t be inside of the mruby-core.
To indicate that some features won’t be ever implemented inside of the mruby-core the new Exception
NotImplementedError was implemented as a sub-class of
An important mruby feature from my point of view is the focus of customization. For this, mruby provides include/mrbconf.h which provides the possibility to customize the following options:
Another commit of Masaki Muranaka improves the test framework which I had previously added to mruby. On his Twitter account he is complaining that the test coverage is less than sufficient at the moment. I completely agree with this statement. The basic problem is of course that mruby wasn’t test-driven developed but is partly based on the CRuby source code. I think the only way to improve this situation is by adding one test at a time for a very long time. Slowly we will get a sufficient coverage in that way. Already now some people reporting bugs based on the mrbtest tool.
Another construction area would be an additional test environment in mruby which is covering the C API of mruby. I hope that there will be a fruitful discussion about this.