From: v.ondruch@... Date: 2021-01-25T16:45:22+00:00 Subject: [ruby-core:102239] [Ruby master Feature#16978] Ruby should not use realpath for __FILE__ Issue #16978 has been updated by vo.x (Vit Ondruch). Dan0042 (Daniel DeLorme) wrote in #note-12: > I think this is a bug and should be fixed, but IMO the proper fix is to use realpath for `__FILE__` This is though one thinking about this again, but you are probably right. Maybe the biggest concern is that the behavior is inconsistent. If the `require` and `__FILE__` used `realpath`, I think the example in #16978-11 would work as you said. ---------------------------------------- Feature #16978: Ruby should not use realpath for __FILE__ https://bugs.ruby-lang.org/issues/16978#change-90089 * 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: