Bug #13126: __dir__ in eval returns nil

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 2.3.3p222 (2016-11-21 revision 56859) [x86_64-linux]
• Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN

[metadeus (Artem Shein)]

$ ruby -e 'eval "p File.dirname(__FILE__); p __dir__"'
"."
nil

[shyouhei (Shyouhei Urabe)]

• Status changed from Open to Feedback

Can you show us your expectation? Should what be the value for __dir__ inside of an eval?

[metadeus (Artem Shein)]

Shyouhei Urabe wrote:

Can you show us your expectation? Should what be the value for __dir__ inside of an eval?

It should be the same as File.dirname(__FILE__) or at least File.dirname(File.realpath(__FILE__)) (like your documentation say).

[nobu (Nobuyoshi Nakada)]

Artem Shein wrote:

It should be the same as File.dirname(__FILE__) or at least File.dirname(File.realpath(__FILE__)) (like your documentation say).

When the third argument is not given, __FILE__ in eval is "(eval)".
Do you mean that __dir__ should be "."?

[metadeus (Artem Shein)]

Nobuyoshi Nakada wrote:

When the third argument is not given, __FILE__ in eval is "(eval)".
Do you mean that __dir__ should be "."?

No, I mean that documentation is saying:
"The return value equals to File.dirname(File.realpath(__FILE__))." here: http://ruby-doc.org/core-2.3.0/Kernel.html#method-i-__dir__

I've replaced the "File.dirname(File.realpath(__FILE__))" in my source code with "__dir__" and got different result. I don't care about the exact value, but I expect it to be the same.

[nobu (Nobuyoshi Nakada)]

Artem Shein wrote:

I've replaced the "File.dirname(File.realpath(__FILE__))" in my source code with "__dir__" and got different result. I don't care about the exact value, but I expect it to be the same.

The former also does not work in eval as expected unless a real path name is given.
Please elaborate on the concrete code.

[jeremyevans0 (Jeremy Evans)]

• Status changed from Feedback to Closed