Jeremy Evans c5c05460ac Warn on access/modify of $SAFE, and remove effects of modifying $SAFE ... This removes the security features added by $SAFE = 1, and warns for access or modification of $SAFE from Ruby-level, as well as warning when calling all public C functions related to $SAFE. This modifies some internal functions that took a safe level argument to no longer take the argument. rb_require_safe now warns, rb_require_string has been added as a version that takes a VALUE and does not warn. One public C function that still takes a safe level argument and that this doesn't warn for is rb_eval_cmd. We may want to consider adding an alternative method that does not take a safe level argument, and warn for rb_eval_cmd.		2019-11-18 01:00:25 +02:00
..
available_ole.rb
err_in_callback.rb
orig_data.csv
test_err_in_callback.rb
test_folderitem2_invokeverb.rb
test_nil2vtempty.rb
test_ole_methods.rb
test_propertyputref.rb
test_thread.rb
test_win32ole.rb	Warn on access/modify of $SAFE, and remove effects of modifying $SAFE	2019-11-18 01:00:25 +02:00
test_win32ole_event.rb	Warn on access/modify of $SAFE, and remove effects of modifying $SAFE	2019-11-18 01:00:25 +02:00
test_win32ole_method.rb
test_win32ole_method_event.rb
test_win32ole_param.rb
test_win32ole_param_event.rb
test_win32ole_record.rb
test_win32ole_type.rb
test_win32ole_type_event.rb
test_win32ole_typelib.rb
test_win32ole_variable.rb
test_win32ole_variant.rb
test_win32ole_variant_m.rb
test_win32ole_variant_outarg.rb
test_word.rb