ruby-under-a-microscope icon indicating copy to clipboard operation
ruby-under-a-microscope copied to clipboard

Code Samples for Ruby Under A Microscope - Learning Ruby Internals Through Experiment

Results 15 ruby-under-a-microscope issues
Sort by recently updated
recently updated
newest added

> by using something called a **“catch table” A** catch table “catch table”. A

> Just like Ruby itself, YARV has **it** own control structures its

> Lexical scope refers to the class or module **the** you are currently defining methods for. that

> **The** works the same way This

> look in the **org.jruby.compile** package org.jruby.compiler

This second stack represents the path through your Ruby program YARV has taken and it’s current location. should be => This second stack represents the path through your Ruby program...

It not only has to track the arguments and return values for it’s own internal instructions Should be => It not only has to track the arguments and return values...

I save it in code_value Should be => I save it in function_value

Specifically, this allows the puts statement to access the str2 variable from the parent scope. Should be => Specifically, this allows the puts statement to access the str variable from...