Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005197OCamlOCaml generalpublic2010-12-15 07:592011-05-17 17:04
Reporterguesdon 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusacknowledgedResolutionopen 
PlatformOSOS Version
Product Version3.12.0 
Target VersionFixed in Version 
Summary0005197: Ability to define --foo= options in Arg
DescriptionHello,

It seems that the standard way to define and use command line options is the following:
- one-char options which take an argument are used with the form
  -f myarg
- long options which take an argument are used with the form
  --foo=myarg

But the Arg module doesn't allow to define the second form. It allows only
  --foo myarg

Would it be possible to allow the specification of such options ? Maybe by adding constructors to the Arg.spec type ?

Maxence
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0005906)
doligez (manager)
2011-05-17 17:04

I don't understand the need to annoy your users by forcing them to type = instead of the large easy-to-find space bar...

The best way to implement this without polluting arg.mli too much is probably to add an optional argument to parse and parse_argv to tell them to accept = as a separator between flag and argument.

- Issue History
Date Modified Username Field Change
2010-12-15 07:59 guesdon New Issue
2011-05-17 17:04 doligez Note Added: 0005906
2011-05-17 17:04 doligez Status new => acknowledged


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker