From: tenderlove@... Date: 2018-12-10T19:48:37+00:00 Subject: [ruby-core:90407] [Ruby trunk Feature#15287] New TracePoint events to support loading features Issue #15287 has been updated by tenderlovemaking (Aaron Patterson). I agree with @eregon. The user has to subscribe to the "compiled_script" event, so the fact that the script has been compiled is already known. For example: ~~~ ruby tp = TracePoint.new(:script_compiled) do |e| p e.compiled_eval_script end tp.enable eval <<-eocode def omglolwut p :hello end eocode ~~~ When the tracepoint executes, we already know it's for a "compiled_script". So "compiled_eval_script" seems redundant. Just "eval_script", or "eval_source" seems good enough. ---------------------------------------- Feature #15287: New TracePoint events to support loading features https://bugs.ruby-lang.org/issues/15287#change-75556 * Author: ko1 (Koichi Sasada) * Status: Closed * Priority: Normal * Assignee: ko1 (Koichi Sasada) * Target version: 2.6 ---------------------------------------- # Abstract I propose the following new TracePoint events: * `loaded` (invoked after `require`/`load`) * `method_added` (invoked after method definition) # Background Sometimes we need to hook loading iseq. For example, checking loading files and so on. Also we want to know what kind of methods are defined. For both purpose, we can use some hook methods such as `Module#method_added` and so on. However, defining methods we can override this features. So that if we have two tools/libraries using this feature, they can be conflicted. # Proposal Introduce new TracePoint events: * `loaded` (invoked after `require`/`load`) * `method_added` (invoked after method definition) Also the following methods can be added: * Active only `loaded` event: * `TracePoint#loaded_feature` returns feature name. * `TracePoint#loaded_iseq` returns `RubyVM::InstructionSequence` object (MRI only, internal feature) # Optional proposal Add `class_added` alias name for `class` event. -- https://bugs.ruby-lang.org/ Unsubscribe: