BETAmodules.com is in beta — open to partnerships & joint ventures.Build with us
modules.com
⌘K

clip

v1.0.2RubyGems· Ruby

You like command-line parsing, but you hate all of the bloat. Why should you have to create a Hash, then create a parser, fill the Hash out then throw the parser away (unless you want to print out a usage message) and deal with a Hash? Why, for Pete's sake, should the parser and the parsed values be handled by two different objects?

The verdict
Abandoned. Last published 16 years ago. No recent activity — look for a maintained alternative.
No recent activity — look for a maintained alternative.
Live from the RubyGems registry · derived rules, not AI
How it scores
MaintenanceAbandoned
PopularityNiche
SecurityClean
LicenseUnknown
DepsZero deps
Maintenance
Last published 16 years ago.
Popularity
9 downloads / week
Security
No known advisories for this version (OSV).
License
No license declared.
Dependencies
No runtime dependencies
Recent releases
  • 1.0.216 years ago
  • 0.0.116 years ago
  • 0.0.216 years ago
  • 0.0.316 years ago
  • 0.0.516 years ago
  • 0.0.616 years ago
  • 1.0.016 years ago
  • 1.0.116 years ago
clip — You like command-line parsing, but you hate all of the bloat. Why should you have to create a Hash, then create a parser, fill the Hash out then throw the parser away (unless you want to print out a usage message) and deal with a Hash? Why, for Pete's sake, should the parser and the parsed values be handled by two different objects? (Ruby / RubyGems) · Modules