OptParse 0.7.4 contains a 'module_function' statement on line 639, but 
it's called from within a class. As a result:

   dave[ruby/optparse-0.7.4 23:10:55] ruby opttest.rb
   /tc/usr/lib/ruby/site_ruby/optparse.rb:639: undefined
          method `module_function' for OptionParser:Class (NameError)
        from opttest.rb:1:in `require'
        from opttest.rb:1


This appears to have been changed in eval.c 1.75 on Jul-15:

     dave[ruby/ruby 23:14:38] cvs diff -r 1.74 -r1.75 eval.c
     Index: eval.c
     ===================================================================
     RCS file: /home/cvs/ruby/eval.c,v
     retrieving revision 1.74
     retrieving revision 1.75
     diff -r1.74 -r1.75
     6c6
     <   $Date: 2000/07/12 06:06:45 $
     ---
     >   $Date: 2000/07/14 04:34:35 $
     80a81
     > static VALUE rb_cUnboundMethod;
     5559a5561,5563
     >     rb_undef_method(rb_cClass, "include");
     >     rb_undef_method(rb_cClass, "module_function");

     +  lots of unbound method stuff


I have no idea if this is a Ruby problem or an OptParse problem.


Regards


Dave