2

__FILE__返回当前 Ruby 脚本文件的路径。

一个潜在的重要问题是,如果使用binding.pry,则__FILE__计算结果为(pry)__FILE__根据是否在binding.pry. 例如,

$stdout.print "****************************************\n\n"
$stdout.print "FILE: #{__FILE__}\n\n"
$stdout.print "****************************************\n\n"

binding.pry

当脚本在 处暂停时binding.pry,我得到:

__FILE__
# >> (pry)

有没有人知道任何机制来获取当前文件的路径,即使在上下文中binding.pry

4

2 回答 2

2

使用_file_而不是__FILE__. 例如,给定两个文件:

# foo.rb
require 'pry'
require './bar'
binding.pry
b = Bar.new

和:

# bar.rb
require 'pry'
class Bar
  def initialize
    binding.pry
  end
end

运行它们ruby foo.rb

ruby foo.rb

From: /Users/username/foo.rb @ line 3 :

    1:     require 'pry'
    2:     require './bar'
 => 3:     binding.pry
    4:     b = Bar.new

(main):1 ⇒ _file_
=> "/Users/username/foo.rb"
(main):2 ⇒ exit

From: /Users/username/bar.rb @ line 4 Bar#initialize:

    3: def initialize
 => 4:   binding.pry
    5: end

(#<Bar:0x00007fbb6caaff08>):1 ⇒ _file_
=> "/Users/username/bar.rb"

_file_任何其他局部变量名称都可以在binding.local_variables.

于 2018-12-14T00:55:17.280 回答
1

Sergio Tulentsev 提出了一个简单的建议,__FILE__在调用之前分配给一个变量binding.pry

anothermh,提到_file_它在绑定撬中可用。

最后,我结合了两个答案:

# When in the context of binding.pry, __FILE__ resolves to '(pry)',
# binding contains the local variable _file_ which always resolves to
# the current file, even when being evaluated in the context of binding.pry .
# _file_ is only available, in binding. This does the trick:

current_file = __FILE__.downcase == '(pry)' ? _file_ : __FILE__
于 2018-12-14T15:32:19.983 回答