From: v.ondruch@... Date: 2020-06-23T07:29:36+00:00 Subject: [ruby-core:98920] [Ruby master Bug#16978] Ruby should not use realpath for __FILE__ Issue #16978 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Bug #16978: Ruby should not use realpath for __FILE__ https://bugs.ruby-lang.org/issues/16978 * Author: vo.x (Vit Ondruch) * Status: Open * Priority: Normal * ruby -v: ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- 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: