lazy requires

[aidy]

Hi,

Are lazy requires generally a good idea

def require_files(path)
dir = File.dirname(__FILE__)
Dir[File.expand_path("#{dir}/#{path}")].uniq.each do |file|
require file
end
end

?

Thanks

Aidy

 

[Trans]

Hi,

Are lazy requires generally a good idea

def require_files(path)
=A0 dir =3D File.dirname(__FILE__)
=A0 Dir[File.expand_path("#{dir}/#{path}")].uniq.each do |file|
=A0 =A0 require file
=A0 end
end

Why do you call that lazy? Do you mean "dynamic" requires?

 

[Ron Fox]

Define good.

Hi,

Are lazy requires generally a good idea

def require_files(path)
dir = File.dirname(__FILE__)
Dir[File.expand_path("#{dir}/#{path}")].uniq.each do |file|
require file
end
end

?

Thanks

Aidy

 

[Stephen Celis]

Hi,

Are lazy requires generally a good idea

def require_files(path)
dir = File.dirname(__FILE__)
Dir[File.expand_path("#{dir}/#{path}")].uniq.each do |file|
require file
end
end

?

I also am not sure what you mean by "lazy" or "good", but offer this:

Requiring a full path can become messy with double requires if you
require the same file anywhere else in your project. It is sometimes
preferred to add the dir to your load paths and require the file's
base name, instead.

Other things to consider

- Array#uniq isn't needed here; a globbed path will return all files
only once.
- "map" might be a better choice than "each", as you can determine
from output the state of all required libs.

Stephen

 

[Erik Hollensbe]

Hi,

Are lazy requires generally a good idea

def require_files(path)
dir = File.dirname(__FILE__)
Dir[File.expand_path("#{dir}/#{path}")].uniq.each do |file|
require file
end
end

It's certainly accepted practice, but with all things you need to ask if
it's necessary.

If you know the files in the path you want, it's much more reliable to
specify them.