[#56333] [CommonRuby - Feature #8723][Open] Array.any? predicate returns true for empty array. — "nurettin (Nurettin Onur TUGCU)" <onurtugcu@...>

12 messages 2013/08/02

[#56368] [ruby-trunk - Bug #8730][Open] "rescue Exception" rescues Timeout::ExitException — "takiuchi (Genki Takiuchi)" <genki@...21g.com>

15 messages 2013/08/04

[#56407] [ruby-trunk - misc #8741][Open] email notification on bugs.ruby-lang.org is broken — "rits (First Last)" <redmine@...>

18 messages 2013/08/05

[#56524] [ruby-trunk - Bug #8770][Open] [PATCH] process.c: avoid EINTR from Process.spawn — "normalperson (Eric Wong)" <normalperson@...>

19 messages 2013/08/10

[#56536] [ruby-trunk - Feature #8772][Open] Hash alias #| merge, and the case for Hash and Array polymorphism — "trans (Thomas Sawyer)" <redmine@...>

24 messages 2013/08/11

[#56544] [ruby-trunk - Bug #8774][Open] rb_file_dirname return wrong encoding string when dir is "." — jiayp@... (贾 延平) <jiayp@...>

10 messages 2013/08/11

[#56569] [ruby-trunk - Feature #8781][Open] Use require_relative() instead of require() if possible — "ko1 (Koichi Sasada)" <redmine@...>

31 messages 2013/08/12
[#56582] [ruby-trunk - Feature #8781] Use require_relative() instead of require() if possible — "drbrain (Eric Hodel)" <drbrain@...7.net> 2013/08/12

[#56584] Re: [ruby-trunk - Feature #8781] Use require_relative() instead of require() if possible — SASADA Koichi <ko1@...> 2013/08/12

(2013/08/13 2:25), drbrain (Eric Hodel) wrote:

[#56636] Re: [ruby-trunk - Feature #8781] Use require_relative() instead of require() if possible — Aaron Patterson <tenderlove@...> 2013/08/16

On Tue, Aug 13, 2013 at 07:38:01AM +0900, SASADA Koichi wrote:

[#56634] [ruby-trunk - Feature #8788][Open] use eventfd on newer Linux instead of pipe for timer thread — "normalperson (Eric Wong)" <normalperson@...>

11 messages 2013/08/16

[#56648] [ruby-trunk - Bug #8795][Open] "Null byte in string error" on Marshal.load — "mml (McClain Looney)" <m@...>

17 messages 2013/08/16

[#56824] [ruby-trunk - Feature #8823][Open] Run trap handler in an independent thread called "Signal thread" — "ko1 (Koichi Sasada)" <redmine@...>

14 messages 2013/08/27

[#56878] [ruby-trunk - misc #8835][Open] Introducing a semantic versioning scheme and branching policy — "knu (Akinori MUSHA)" <knu@...>

11 messages 2013/08/30

[#56890] [ruby-trunk - Feature #8839][Open] Class and module should return the class or module that was opened — "headius (Charles Nutter)" <headius@...>

26 messages 2013/08/30

[#56894] [ruby-trunk - Feature #8840][Open] Yielder#state — "marcandre (Marc-Andre Lafortune)" <ruby-core@...>

14 messages 2013/08/30

[ruby-core:56674] Re: [ruby-trunk - Feature #8781] Use require_relative() instead of require() if possible

From: Aaron Patterson <tenderlove@...>
Date: 2013-08-17 04:13:07 UTC
List: ruby-core #56674
On Sat, Aug 17, 2013 at 07:17:50AM +0900, trans (Thomas Sawyer) wrote:
> 
> Issue #8781 has been updated by trans (Thomas Sawyer).
> 
> 
> > $ echo "require_relative '../../foo'" > lib/foo/bar/baz.rb
> 
> Seriously? That is not a real use case. Proper use of require_relative is downward, not upward.

*sigh*

First, it *is* a real use case (as in, people actually use it in *real*
projects):

[aaron@higgins ruby (trunk)]$ git grep require_relative | grep '\.\.' | wc -l
      45
[aaron@higgins ruby (trunk)]$

If Ruby's source code isn't enough examples for you, try a GitHub seach:

  https://github.com/search?q=require_relative+..&type=Code&ref=searchresults

It's not up to you what is "proper" use.

Second, my point remains valid whether you go down or up.  Let's do
another example.

"foo.rb" depends on "foo/bar/baz.rb".

$ mkdir -p lib/foo/bar
$ touch lib/foo/bar/baz.rb
$ echo "require_relative 'foo/bar/baz'" > lib/foo.rb
$ ruby -I lib -rfoo -e 0
$ mv lib/foo.rb lib/foo/
$ ruby -I lib -rfoo/foo -e 0
/Users/aaron/git/example/lib/foo/foo.rb:1:in `require_relative': cannot load such file -- /Users/aaron/git/example/lib/foo/foo/bar/baz (LoadError)
        from /Users/aaron/git/example/lib/foo/foo.rb:1:in `<top (required)>'
        from /Users/aaron/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require'
        from /Users/aaron/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require'
$

If we move "foo.rb", we still have to change the call to
"require_relative" **even though the file we depend on did not change**.

Here is the same example just using `require`:

$ mkdir -p lib/foo/bar
$ echo "require 'foo/bar/baz'" > lib/foo.rb
$ touch lib/foo/bar/baz.rb
$ ruby -I lib -rfoo -e 0
$ mv lib/foo.rb lib/foo/
$ ruby -I lib -rfoo/foo -e 0
$

Again, "foo.rb" is completely independent of the filesystem.  The files
it depends on did not change, so it did not have to change.

I am uncertain how to make the coupling between "require_relative" and
the filesystem more clear than this.

-- 
Aaron Patterson
http://tenderlovemaking.com/

In This Thread