=begin
Currently the definition of the load method in iseq.c is commented out "because there is no verifier". The fact that InstructionSequence::compile.to_a has no assembling counterpart that can turn the serialized output back into an iseq object greatly restricts the usefulness InstructionSequence. For example, there is no way to disassemble a method, send it over the network and then assemble it again. The method should be re-enabled even though there is no verifier yet.
=end
Currently the definition of the load method in iseq.c is commented out "because there is no verifier". The fact that InstructionSequence::compile.to_a has no assembling counterpart that can turn the serialized output back into an iseq object greatly restricts the usefulness InstructionSequence. For example, there is no way to disassemble a method, send it over the network and then assemble it again. The method should be re-enabled even though there is no verifier yet.
You can write an extension in C with "ruby_iseq_load()".
Note that I can't guarantee the compatibility of bytecode set and
format. In fact, some instructions may changed in 1.9.2 because of lack
of functionality.