Bug #2782: Binding#eval not completely indicative of its binding

• Status: Closed
• Assignee: mame (Yusuke Endoh)
• Target version: 1.9.2

[trans (Thomas Sawyer)]

=begin
binding.eval("FILE") does not return the file from which the binding was created.

Given the purpose of binding it should hold that:

FILE == binding.eval("FILE")
=end

[zenspider (Ryan Davis)]

On Feb 23, 2010, at 05:18 , Thomas Sawyer wrote:

Bug #2782: Binding#eval not completely indicative of its binding
http://redmine.ruby-lang.org/issues/show/2782

Author: Thomas Sawyer
Status: Open, Priority: Normal
Category: core
ruby -v: 1.9.1

binding.eval("__FILE__") does not return the file from which the binding was created.

Given the purpose of binding it should hold that:

 __FILE__ == binding.eval("__FILE__")

Just my two cents: (yen?)

__FILE__ is expanded at parse time directly into the parse tree. As such, it isn't really a variable or a constant, just a placeholder. I don't think it is going to be easy to make it act like a constant for Binding#eval.

[mame (Yusuke Endoh)]

• Assignee set to matz (Yukihiro Matsumoto)

Hi,

2010/2/23 Thomas Sawyer [e-mail]:

binding.eval("__FILE__") does not return the file from which the binding was created.

Given the purpose of binding it should hold that:

  __FILE__ == binding.eval("__FILE__")

In the current semantics, I guess binding does not includes
the imformation of filename and lineno.

At least, this is not a bug. I moved the ticket to Feature
tracker.

--
Yusuke ENDOH [e-mail]

[mame (Yusuke Endoh)]

• Target version set to 3.0

[mame (Yusuke Endoh)]

• Assignee changed from matz (Yukihiro Matsumoto) to mame (Yusuke Endoh)
• Target version changed from 3.0 to 1.9.2

Hi,

2010/4/11 Yusuke Endoh [e-mail]:

2010/2/23 Thomas Sawyer [e-mail]:

binding.eval("__FILE__") does not return the file from which the binding was created.

Given the purpose of binding it should hold that:

  __FILE__ == binding.eval("__FILE__")

In the current semantics, I guess binding does not includes
the imformation of filename and lineno.

At least, this is not a bug. ?I moved the ticket to Feature
tracker.

Sorry I was wrong. I didn't know 1.8 preserves the filename.
I agree that this is a bug.

And this ticket duplicates #1769. I've suggested a patch in that ticket.

--
Yusuke Endoh [e-mail]

[mame (Yusuke Endoh)]

• Status changed from Open to Closed

This issue was solved with changeset r27716.
Yuki, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.