--- Edwin Pratomo <[EMAIL PROTECTED]> wrote: > good day jim and all > > currently rake uses getoptlong to parse command line options. the problem > with > this is that getoptlong destructively consumes ARGV, which means checking > ARGV > in a rakefile won't find any previously passed options. > > why would we need to check ARGV in rakefile? one possible case is to make use > of rake's options such as -q or -v. so users might pass -qq or -vvv and a > rakefile will print as much (or as little) output as those options are given. > > so i'd suggest to use optparse instead, as optparse supports non-destructive > parsing.
attached is a patch for this. against svn trunk, rev 642.
rgds,
Edwin.
________________________________________________________
Bergabunglah dengan orang-orang yang berwawasan, di di bidang Anda! Kunjungi
Yahoo! Answers saat ini juga di http://id.answers.yahoo.com/
rake-optparse.patch
Description: 51425519-rake-optparse.patch
_______________________________________________ Rake-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/rake-devel
