[ruby-core:80253] [Ruby trunk Bug#13337] Eval and Later Defined Local Variables

[ruby-core:80253] [Ruby trunk Bug#13337] Eval and Later Defined Local Variables

[faraz.yashar]

Issue #13337 has been reported by faraz (Faraz Yashar).

----------------------------------------
Bug #13337: Eval and Later Defined Local Variables
https://bugs.ruby-lang.org/issues/13337

* Author: faraz (Faraz Yashar)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.4.0
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
I've noticed the following behavior with eval:

~~~ ruby
def example
  eval("foo") # => nil, but would expect a NameError
  eval("bar") # => NameError
  foo = 1
end
~~~

I'm assuming this behavior is expected, since "eval" executes in the context of the existing YARV instructions and local table, but I'm not certain since I haven't seen this behavior documented anywhere. 



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

[ruby-core:81253] [Ruby trunk Bug#13337] Eval and Later Defined Local Variables

[ko1]

Issue #13337 has been updated by ko1 (Koichi Sasada).


This is specification.

(1) parse `example` method and define `foo`.
(2) In `eval` method, compile given string (`"foo"`) and defined `foo` was used (without any problem).

So it is documentation issue.
Can anyone write about it?


----------------------------------------
Bug #13337: Eval and Later Defined Local Variables
https://bugs.ruby-lang.org/issues/13337#change-64914

* Author: faraz (Faraz Yashar)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.4.0
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
I've noticed the following behavior with eval:

~~~ ruby
def example
  eval("foo") # => nil, but would expect a NameError
  eval("bar") # => NameError
  foo = 1
end
~~~

I'm assuming this behavior is expected, since "eval" executes in the context of the existing YARV instructions and local table, but I'm not certain since I haven't seen this behavior documented anywhere. 



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

[ruby-core:93342] [Ruby trunk Bug#13337] Eval and Later Defined Local Variables

[merch-redmine]

Issue #13337 has been updated by jeremyevans0 (Jeremy Evans).

File doc-eval-local-var.patch added

ko1 (Koichi Sasada) wrote:
> This is specification.
> 
> (1) parse `example` method and define `foo`.
> (2) In `eval` method, compile given string (`"foo"`) and defined `foo` was used (without any problem).
> 
> So it is documentation issue.
> Can anyone write about it?

Attached is a documentation patch.  However, a committer with more knowledge of the internals should probably check to see if it is technically accurate.

----------------------------------------
Bug #13337: Eval and Later Defined Local Variables
https://bugs.ruby-lang.org/issues/13337#change-78847

* Author: faraz (Faraz Yashar)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.4.0
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
I've noticed the following behavior with eval:

~~~ ruby
def example
  eval("foo") # => nil, but would expect a NameError
  eval("bar") # => NameError
  foo = 1
end
~~~

I'm assuming this behavior is expected, since "eval" executes in the context of the existing YARV instructions and local table, but I'm not certain since I haven't seen this behavior documented anywhere. 

---Files--------------------------------
doc-eval-local-var.patch (1.63 KB)


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

[ruby-core:93344] [Ruby trunk Bug#13337] Eval and Later Defined Local Variables

[chris]

Issue #13337 has been updated by chrisseaton (Chris Seaton).


This is as specified here

https://github.com/ruby/spec/blob/db74bf3313b4d49650417ba91b4e2d67cc253dc5/core/kernel/eval_spec.rb#L31-L68

----------------------------------------
Bug #13337: Eval and Later Defined Local Variables
https://bugs.ruby-lang.org/issues/13337#change-78849

* Author: faraz (Faraz Yashar)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.4.0
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
I've noticed the following behavior with eval:

~~~ ruby
def example
  eval("foo") # => nil, but would expect a NameError
  eval("bar") # => NameError
  foo = 1
end
~~~

I'm assuming this behavior is expected, since "eval" executes in the context of the existing YARV instructions and local table, but I'm not certain since I haven't seen this behavior documented anywhere. 

---Files--------------------------------
doc-eval-local-var.patch (1.63 KB)


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

[ruby-core:93355] [Ruby trunk Bug#13337] Eval and Later Defined Local Variables

[nobu]

Issue #13337 has been updated by nobu (Nobuyoshi Nakada).


jeremyevans0 (Jeremy Evans) wrote:
> Attached is a documentation patch. 

Seems fine.

A question:
> However, local variables set inside the call to +eval+ will not be reflected in the surrounding scope.

Isn't "set" vague a little, between "defined" an "assigned"?



----------------------------------------
Bug #13337: Eval and Later Defined Local Variables
https://bugs.ruby-lang.org/issues/13337#change-78865

* Author: faraz (Faraz Yashar)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.4.0
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
I've noticed the following behavior with eval:

~~~ ruby
def example
  eval("foo") # => nil, but would expect a NameError
  eval("bar") # => NameError
  foo = 1
end
~~~

I'm assuming this behavior is expected, since "eval" executes in the context of the existing YARV instructions and local table, but I'm not certain since I haven't seen this behavior documented anywhere. 

---Files--------------------------------
doc-eval-local-var.patch (1.63 KB)


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

[ruby-core:93362] [Ruby trunk Bug#13337] Eval and Later Defined Local Variables

[nobu]

Issue #13337 has been updated by nobu (Nobuyoshi Nakada).


"local variables assigned inside the call to +eval+" sounds like a just assignment to a local variable defined outside, doesn't it?

----------------------------------------
Bug #13337: Eval and Later Defined Local Variables
https://bugs.ruby-lang.org/issues/13337#change-78877

* Author: faraz (Faraz Yashar)
* Status: Closed
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.4.0
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
I've noticed the following behavior with eval:

~~~ ruby
def example
  eval("foo") # => nil, but would expect a NameError
  eval("bar") # => NameError
  foo = 1
end
~~~

I'm assuming this behavior is expected, since "eval" executes in the context of the existing YARV instructions and local table, but I'm not certain since I haven't seen this behavior documented anywhere. 

---Files--------------------------------
doc-eval-local-var.patch (1.63 KB)


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

[ruby-core:93363] [Ruby trunk Bug#13337] Eval and Later Defined Local Variables

[merch-redmine]

Issue #13337 has been updated by jeremyevans0 (Jeremy Evans).


nobu (Nobuyoshi Nakada) wrote:
> "local variables assigned inside the call to +eval+" sounds like a just assignment to a local variable defined outside, doesn't it?

It could definitely be interpreted that way.  I'll reword it to make it more clear. Thanks!

----------------------------------------
Bug #13337: Eval and Later Defined Local Variables
https://bugs.ruby-lang.org/issues/13337#change-78878

* Author: faraz (Faraz Yashar)
* Status: Closed
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.4.0
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
I've noticed the following behavior with eval:

~~~ ruby
def example
  eval("foo") # => nil, but would expect a NameError
  eval("bar") # => NameError
  foo = 1
end
~~~

I'm assuming this behavior is expected, since "eval" executes in the context of the existing YARV instructions and local table, but I'm not certain since I haven't seen this behavior documented anywhere. 

---Files--------------------------------
doc-eval-local-var.patch (1.63 KB)


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