Issue #6724 has been updated by shyouhei (Shyouhei Urabe).


I really like this feature.  I have this exact patch applied to my local ruby binary.

But having used it a while, I found that ISeq loading is not what an application programmer would try.  It is rather a tool that a library author thirst for.  So I doubt a user is really the one who should be pushed the responsibility.
----------------------------------------
Bug #6724: waaaaaaant! (
https://bugs.ruby-lang.org/issues/6724#change-27957

Author: zenspider (Ryan Davis)
Status: Open
Priority: Normal
Assignee: ko1 (Koichi Sasada)
Category: 
Target version: 
ruby -v: 2.x


GIMME GIMME GIMME! waaaaaant... We don't _need_ a verifier. User responsibility... etc etc.


Can I commit this??? PLEEEEEEASE???

Index: iseq.c
===================================================================
--- iseq.c	(revision 36369)
+++ iseq.c	(working copy)
@@ -1585,9 +1585,7 @@
     rb_define_method(rb_cISeq, "marshal_load", iseq_marshal_load, 1);
 #endif
 
-    /* disable this feature because there is no verifier. */
-    /* rb_define_singleton_method(rb_cISeq, "load", iseq_s_load, -1); */
-    (void)iseq_s_load;
+    rb_define_singleton_method(rb_cISeq, "load", iseq_s_load, -1);
 
     rb_define_singleton_method(rb_cISeq, "compile", iseq_s_compile, -1);
     rb_define_singleton_method(rb_cISeq, "new", iseq_s_compile, -1);



-- 
http://bugs.ruby-lang.org/