From: sylvain.joyeux@...4x.org Date: 2016-09-19T12:38:38+00:00 Subject: [ruby-core:77314] [Ruby trunk Bug#9244] unexpected behaviour of 'require' when $LOAD_PATH gets changed Issue #9244 has been updated by Sylvain Joyeux. ruby -v changed from 1.9.3p484, 2.0.0p353, 2.1.2 2.1.6p336 2.2.1p85 to 1.9.3p484, 2.0.0p353, 2.1.2 2.1.6p336 2.2.1p85 2.3.1p112 Backport deleted (1.9.3: UNKNOWN, 2.0.0: UNKNOWN) and on 2.3.1 ---------------------------------------- Bug #9244: unexpected behaviour of 'require' when $LOAD_PATH gets changed https://bugs.ruby-lang.org/issues/9244#change-60554 * Author: Sylvain Joyeux * Status: Feedback * Priority: Normal * Assignee: * ruby -v: 1.9.3p484, 2.0.0p353, 2.1.2 2.1.6p336 2.2.1p85 2.3.1p112 * Backport: ---------------------------------------- For the purpose of reproducing the error, let's assume that I have two folders ```a``` and ```b``` which both contain a file ```test.rb``` In the following script, ```b/test.rb``` will NOT get loaded: ``` $LOAD_PATH.unshift File.join(Dir.pwd, 'a') require 'test.rb' $LOAD_PATH.unshift File.join(Dir.pwd, 'b') require 'test.rb' ``` I would have expected this behaviour before, when required files were not registered through their absolute paths in $LOADED_FEATURES. Right now, I find it confusing. -- https://bugs.ruby-lang.org/ Unsubscribe: