Jeremy Evans b78a345bd6 Only set RB_PASS_CALLED_KEYWORDS in C functions called directly from Ruby ... It is not safe to set this in C functions that can be called from other C functions, as in the non argument-delegation case, you can end up calling a Ruby method with a flag indicating keywords are set without passing keywords. Introduce some new *_kw functions that take a kw_splat flag and use these functions to set RB_PASS_CALLED_KEYWORDS in places where we know we are delegating methods (e.g. Class#new, Method#call)		2019-09-14 01:49:33 -07:00
..
backward	fix CentOS 6 compile error	2019-09-10 12:25:36 +09:00
assert.h	Revert "Always evaluate the expression RUBY_ASSERT_MESG_WHEN just once"	2019-08-05 08:55:09 +09:00
backward.h	Renamed ruby_finalize_{0,1}	2019-08-13 09:47:08 +09:00
debug.h
defines.h	fix CentOS 6 compile error	2019-09-10 12:25:36 +09:00
encoding.h
intern.h	Only set RB_PASS_CALLED_KEYWORDS in C functions called directly from Ruby	2019-09-14 01:49:33 -07:00
io.h	io.c: export rb_io_extract_modeenc	2019-08-14 11:20:58 +09:00
missing.h
onigmo.h
oniguruma.h
re.h
regex.h
ruby.h	Only set RB_PASS_CALLED_KEYWORDS in C functions called directly from Ruby	2019-09-14 01:49:33 -07:00
st.h	struct st_hash_type now free from ANYARGS	2019-08-27 15:52:26 +09:00
subst.h
thread.h
thread_native.h
util.h
version.h
vm.h
win32.h	Fix errno at seeking socket/pipe on Windows	2019-07-25 06:39:40 +09:00