5 Commits

Author	SHA1	Message	Date
dearblue	0e00d8e224	Integrate mruby-binding-eval into mruby-eval ... Currently mruby-eval depends on mruby-binding (formerly mruby-binding-core). Also, `Kernel#eval` can accept `binding` objects. With this in mind, it would be better if `Binding#eval` could also be handled by `mrbgems/mruby-eval`.	2023-04-16 21:44:00 +09:00
Yukihiro "Matz" Matsumoto	11af5db1c3	mruby-binding: renamed from mruby-binding-core ... The dependency is now: mruby-binding-eval: - mruby-binding - mruby-eval mruby-proc-binding: - mruby-binding mruby-eval: - mruby-binding [new]	2023-03-24 12:25:57 +09:00
Yukihiro "Matz" Matsumoto	501b22a2ac	mruby-binding-eval: renamed from mruby-binding ... Since this gem only provides `Binding#eval`.	2023-03-22 15:25:23 +09:00
dearblue	6adbbd8773	Needs mruby-proc-ext by mruby-proc-binding ... The `mruby-proc_source_location()` function used in `src/proc-binding.c` of `mruby-proc-binding` is defined in `mruby-proc-ext`.	2022-10-21 21:44:06 +09:00
dearblue	927615e1f0	Added other methods for Binding ... - Added to `mruby-binding-core` - `Binding#local_variable_defined?` - `Binding#local_variable_get` - `Binding#local_variable_set` - `Binding#local_variables` - `Binding#receiver` - `Binding#source_location` - `Binding#inspect` - Added to `mruby-proc-binding` - `Proc#binding` The reason for separating `Proc#binding` is that core-mrbgems has a method that returns a closure object to minimize possible problems with being able to manipulate internal variables. By separating it as different mrbgem, each user can judge this problem and incorporate it arbitrarily.	2021-02-22 23:32:43 +09:00