Jeff Wood wrote...
> What's up with the funky names ... AND, is there an easy way to just 
> require
> all of them ?
>  I'd like to have all of nano and all of mega easily includable without 
> 400
> separate require statements ( exagerated I know, but still )

In the API docs at nano.rubyforge.org and mega.rubyforge.org, check out the 
documentation for the _files_ nano.rb, nano/base.rb (and mega's 
corresponding files) to see the list of what's included there.

For example, if you just do:
  require 'nano'
or:
  require 'nano/base'
you will get all of these for free:
  a.. nano/kernel/require_nano
  b.. nano/array/to_h
  c.. nano/binding/eval
  d.. nano/binding/self
  e.. nano/binding/caller
  f.. nano/comparable/cmp
  g.. nano/enumerable/collect_with_counter
  h.. nano/enumerable/each_slice
  i.. nano/float/round_off
  j.. nano/float/round_to
  k.. nano/float/round_at
  l.. nano/hash/slice
  m.. nano/hash/to_h
  n.. nano/kernel/fn
  o.. nano/kernel/called
  p.. nano/kernel/here
  q.. nano/matchdata/match
  r.. nano/module/basename
  s.. nano/nilclass/to_f
  t.. nano/nilclass/to_h
  u.. nano/object/metaclass
  v.. nano/proc/to_method
  w.. nano/range/to_r
  x.. nano/regexp/to_re
  y.. nano/string/blank%3F
  z.. nano/string/cmp
  aa.. nano/string/to_re
  ab.. nano/symbol/not
  ac.. nano/time/to_time
Then there's the require_* methods, require_all in particular.

Happy requiring!
Dave