From: eregontp@... Date: 2020-07-09T21:18:38+00:00 Subject: [ruby-core:99101] [Ruby master Feature#16978] Ruby should not use realpath for __FILE__ Issue #16978 has been updated by Eregon (Benoit Daloze). The "main file" (the file passed to `ruby myfile.rb` is also special in that `__FILE__` and `$0` can both be relative paths (basically the same path as passed on the command line). ---------------------------------------- Feature #16978: Ruby should not use realpath for __FILE__ https://bugs.ruby-lang.org/issues/16978#change-86475 * Author: vo.x (Vit Ondruch) * Status: Open * Priority: Normal ---------------------------------------- This is the simplest test case: ~~~ $ mkdir a $ echo "puts __FILE__" > a/test.rb $ ln -s a b $ ruby -Ib -e "require 'test'" /builddir/a/test.rb ~~~ This behavior is problematic, because Ruby should not know nothing about the `a` directory. It was not instructed to use it. I should always refer to the file using the original path and do not dig into the underlying details, otherwise depending on file system setup, one might be forced to used `File.realpath` everywhere trying to use `__FILE__`. -- https://bugs.ruby-lang.org/ Unsubscribe: