summaryrefslogtreecommitdiffhomepage
path: root/mrbgems
diff options
context:
space:
mode:
authordearblue <[email protected]>2020-12-25 23:23:14 +0900
committerdearblue <[email protected]>2020-12-25 23:24:20 +0900
commit88a11d81b0e1773f88dfa764ccc2f7fd0df61cf0 (patch)
treec0ad53e197d95c3021461422a9e837de2e27f568 /mrbgems
parent825c14a0c5e86cc2d33a3f70d3be846660d466f6 (diff)
downloadmruby-88a11d81b0e1773f88dfa764ccc2f7fd0df61cf0.tar.gz
mruby-88a11d81b0e1773f88dfa764ccc2f7fd0df61cf0.zip
Improves out of memory messages for `eval`
The comment says that if `mrb_parse_nstring()` returns `NULL`, it is only out of memory. I'm worried about compatibility if I set the exception class to `NoMemoryError`, so it's still `RuntimeError`.
Diffstat (limited to 'mrbgems')
-rw-r--r--mrbgems/mruby-eval/src/eval.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/mrbgems/mruby-eval/src/eval.c b/mrbgems/mruby-eval/src/eval.c
index d9df8678f..c7a511fe4 100644
--- a/mrbgems/mruby-eval/src/eval.c
+++ b/mrbgems/mruby-eval/src/eval.c
@@ -39,7 +39,7 @@ create_proc_from_string(mrb_state *mrb, const char *s, mrb_int len, mrb_value bi
/* only occur when memory ran out */
if (!p) {
- mrb_raise(mrb, E_RUNTIME_ERROR, "Failed to create parser state.");
+ mrb_raise(mrb, E_RUNTIME_ERROR, "Failed to create parser state (out of memory)");
}
if (0 < p->nerr) {