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
..
lib
sample
depend
extconf.rb
win32ole.c	Warn on access/modify of $SAFE, and remove effects of modifying $SAFE	2019-11-18 01:00:25 +02:00
win32ole.h
win32ole_error.c
win32ole_error.h
win32ole_event.c	Warn on access/modify of $SAFE, and remove effects of modifying $SAFE	2019-11-18 01:00:25 +02:00
win32ole_event.h
win32ole_method.c
win32ole_method.h
win32ole_param.c
win32ole_param.h
win32ole_record.c
win32ole_record.h
win32ole_type.c
win32ole_type.h
win32ole_typelib.c
win32ole_typelib.h
win32ole_variable.c
win32ole_variable.h
win32ole_variant.c
win32ole_variant.h
win32ole_variant_m.c
win32ole_variant_m.h