M
Marc Heiler
require does accept ony word, which should be the name that has
to be required. Since duck typing is en vogue, is it a bad idea to
have require use something like this here instead?
require %w( pp English pathname fileutils abbrev pp digest/md5 yaml)
The reason I write this is because I quite often see this:
%w( pathname fileutils English abbrev pp digest/md5 yaml ).each { |file|
require file }
which some people like to do compared to the a little cumbersome:
require 'pathname'
require 'fileutils'
require 'English'
require 'abbrev'
Is there a reason why require accepts only one arg, and why it doesnt
allow multiple args/Array as arg?
to be required. Since duck typing is en vogue, is it a bad idea to
have require use something like this here instead?
require %w( pp English pathname fileutils abbrev pp digest/md5 yaml)
The reason I write this is because I quite often see this:
%w( pathname fileutils English abbrev pp digest/md5 yaml ).each { |file|
require file }
which some people like to do compared to the a little cumbersome:
require 'pathname'
require 'fileutils'
require 'English'
require 'abbrev'
Is there a reason why require accepts only one arg, and why it doesnt
allow multiple args/Array as arg?