Kernel#require accepting multiple arguments?

[Daniel Schierbeck]

What is the reason that Kernel#require only accepts one filename?
Implementing a version of `require' that can take multiple arguments is
pretty easy:

module Kernel
alias_method :__require__, :require

def require(*filenames)
filenames.all? { |file| __require__(file) }
end
end


Cheers,
Daniel

 

[Stefan Lang]

What is the reason that Kernel#require only accepts one filename?
Implementing a version of `require' that can take multiple
arguments is pretty easy:

module Kernel
alias_method :__require__, :require

def require(*filenames)
filenames.all? { |file| __require__(file) }
end
end

Perhaps to allow version specification in the future.
E.g.:

require 'foo', '>= 1.0.1'

like RubyGems require_gem.

Regards,
Stefan

 

[Yukihiro Matsumoto]

Hi,

In message "Re: Kernel#require accepting multiple arguments?"

|What is the reason that Kernel#require only accepts one filename?

Since we'd like to keep it for "parametrized require" in the future.

matz.

 

[Daniel Schierbeck]

Hi,

In message "Re: Kernel#require accepting multiple arguments?"

|What is the reason that Kernel#require only accepts one filename?

Since we'd like to keep it for "parametrized require" in the future.

matz.

Good enough for me!


Cheers,
Daniel

 

[Eric Hodel]

What is the reason that Kernel#require only accepts one filename?
Implementing a version of `require' that can take multiple
arguments is pretty easy:

module Kernel
alias_method :__require__, :require

def require(*filenames)
filenames.all? { |file| __require__(file) }
end
end

Or you can turn the problem around:

%w[file1 file2].each { |f| require f }