mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
[ci skip] Fix what is pushed to nesting about eval family
This commit is contained in:
parent
9bf9097973
commit
419d259f63
1 changed files with 3 additions and 2 deletions
|
@ -151,9 +151,10 @@ executed, and popped after it.
|
||||||
|
|
||||||
* A singleton class opened with `class << object` gets pushed, and popped later.
|
* A singleton class opened with `class << object` gets pushed, and popped later.
|
||||||
|
|
||||||
* When any of the `*_eval` family of methods is called using a string argument,
|
* When `instance_eval` is called using a string argument,
|
||||||
the singleton class of the receiver is pushed to the nesting of the eval'ed
|
the singleton class of the receiver is pushed to the nesting of the eval'ed
|
||||||
code.
|
code. When `class_eval` or `module_eval` is called using a string argument,
|
||||||
|
the receiver is pushed to the nesting of the eval'ed code.
|
||||||
|
|
||||||
* The nesting at the top-level of code interpreted by `Kernel#load` is empty
|
* The nesting at the top-level of code interpreted by `Kernel#load` is empty
|
||||||
unless the `load` call receives a true value as second argument, in which case
|
unless the `load` call receives a true value as second argument, in which case
|
||||||
|
|
Loading…
Reference in a new issue