opensoul.org - Ruby's require doesn't expand paths Comments

Comment on 'Ruby's require doesn't expand paths' by Jamie Flournoy

2008-05-28T01:03:44Z

I wrote a snippet that automates this, in case you aren’t up for the global search and replace alternative.

http://www.pervasivecode.com/blog/2008/05/16/rails-snippet-require-app-files-only-once/

Comment on 'Ruby's require doesn't expand paths' by Rob Sanheim

2008-04-23T00:56:54Z

This is fixed in 1.9. WIll be very nice to drop the nasty expand_path everywhere.

Comment on 'Ruby's require doesn't expand paths' by Brandon

2008-01-21T01:23:52Z

James,

I think you have that backwards. From the Ruby API docs for #require

The name of the loaded feature is added to the array in $”. A feature will not be loaded if it‘s name already appears in $”.

Also, neither #require or #load behave differently based on if the file is modified.

Comment on 'Ruby's require doesn't expand paths' by James Deville

2008-01-19T05:32:54Z

Another issue is that require is not meant to load a file only once. Load is. If you require a file, change it, and require it again, your changes will be picked up. If you load a file, change it, and load it again, no change. This is on purpose since sometimes you do want to load a file twice.

Comment on 'Ruby's require doesn't expand paths' by James Moore

2008-01-09T18:52:10Z

Another way to solve this is that everyone always does the vanilla

require File.dirname(FILE) + ’/../test_helper’

But add a test_helper.rb file (or files, depending on how many sublevels you have) that then includes the right test_helper.rb.

The advantage to doing it this way is you never have to care how many /../ substrings there are in your paths.

Comment on 'Ruby's require doesn't expand paths' by Eric-Olivier Lamey

2008-01-09T11:52:28Z

I think this behaviour was changed in ruby 1.9.