diff options
| author | 卜部昌平 <shyouhei@ruby-lang.org> | 2019-08-26 14:51:00 +0900 |
|---|---|---|
| committer | 卜部昌平 <shyouhei@ruby-lang.org> | 2019-08-27 15:52:26 +0900 |
| commit | 5c7c2d9951f2512ca10ea38fecc48d8ac67502e6 (patch) | |
| tree | a6a317a81bb40854ebd7dd50cf6d001f7a444fe1 /eval.c | |
| parent | 3cae73133cfec7d5ec3f8058ec647d5163578003 (diff) | |
| download | ruby-5c7c2d9951f2512ca10ea38fecc48d8ac67502e6.tar.gz | |
rb_rescue / rb_rescue2 now free from ANYARGS
After 5e86b005c0f2ef30df2f9906c7e2f3abefe286a2, I now think ANYARGS is
dangerous and should be extinct. This commit deletes ANYARGS from
rb_rescue / rb_rescue2, which revealed many arity / type mismatches.
Diffstat (limited to 'eval.c')
| -rw-r--r-- | eval.c | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -931,8 +931,8 @@ rb_need_block(void) * \ingroup exception */ VALUE -rb_rescue2(VALUE (* b_proc) (ANYARGS), VALUE data1, - VALUE (* r_proc) (ANYARGS), VALUE data2, ...) +rb_rescue2(VALUE (* b_proc) (VALUE), VALUE data1, + VALUE (* r_proc) (VALUE, VALUE), VALUE data2, ...) { enum ruby_tag_type state; rb_execution_context_t * volatile ec = GET_EC(); @@ -1003,8 +1003,8 @@ rb_rescue2(VALUE (* b_proc) (ANYARGS), VALUE data1, * \ingroup exception */ VALUE -rb_rescue(VALUE (* b_proc)(ANYARGS), VALUE data1, - VALUE (* r_proc)(ANYARGS), VALUE data2) +rb_rescue(VALUE (* b_proc)(VALUE), VALUE data1, + VALUE (* r_proc)(VALUE, VALUE), VALUE data2) { return rb_rescue2(b_proc, data1, r_proc, data2, rb_eStandardError, (VALUE)0); |