./devel/hs-cmdargs, Command line argument processing

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 0.10.13, Package name: hs-cmdargs-0.10.13, Maintainer: szptvlfn

This library provides an easy way to define command line parsers.
Most users will want to use the System.Console.CmdArgs.Implicit module,
whose documentation contains an example.

* System.Console.CmdArgs.Explicit provides a way to write command line parsers
for both single mode programs (most programs) and multiple mode programs
(e.g. darcs or cabal). Parsers are defined by constructing a data structure.

* System.Console.CmdArgs.Implicit provides a way to concisely define
command line parsers, up to three times shorter than getopt.
These parsers are translated into the Explicit data type.

* System.Console.CmdArgs.GetOpt provides a wrapper allowing compatiblity
with existing getopt parsers, mapping to the Explicit data type.

For a general reference on what command line flags are commonly used,
see http://www.faqs.org/docs/artu/ch10s05.html.


Master sites:

SHA1: e9477122ccea8d2e0d77d961b191932b2f3e018e
RMD160: 52ec121615ce553d7dbeb22c3c60b9383c0c16ff
Filesize: 62.508 KB

Version history: (Expand)


CVS history: (Expand)


   2015-11-03 04:29:40 by Alistair G. Crooks | Files touched by this commit (1995)
Log message:
Add SHA512 digests for distfiles for devel category

Issues found with existing distfiles:
	distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
	distfiles/fortran-utils-1.1.tar.gz
	distfiles/ivykis-0.39.tar.gz
	distfiles/enum-1.11.tar.gz
	distfiles/pvs-3.2-libraries.tgz
	distfiles/pvs-3.2-linux.tgz
	distfiles/pvs-3.2-solaris.tgz
	distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
   2015-06-04 15:06:12 by Ryosuke Moro | Files touched by this commit (3) | Package updated
Log message:
Update to 0.10.13

CHANGES:
0.10.13
    #24, support Ratio in some places
    https://github.com/ndmitchell/cmdargs/issues/24
0.10.12
    GHC 7.2 compatibility
0.10.11
    #15, never put [brackets] around optional args in Explicit
    https://github.com/ndmitchell/cmdargs/issues/15
   2014-11-23 13:52:33 by Ryosuke Moro | Files touched by this commit (51) | Package updated
Log message:
Bump PKGREVISION for hs-transformers-0.4.2.0
   2014-10-08 23:56:17 by Ryosuke Moro | Files touched by this commit (3) | Package updated
Log message:
Update to 0.10.10

CHANGES:
0.10.10
    #14, fix @ file arguments
	deprecated tyConString
   2014-08-29 16:08:42 by Ryosuke Moro | Files touched by this commit (61)
Log message:
make it clear what package depend on

discussed with wiz@.
   2014-07-28 23:35:23 by Ryosuke Moro | Files touched by this commit (3) | Package updated
Log message:
Update to 0.10.9

CHANGES:
0.10.9
    #10, fix versionArgs (broken in 0.10.8)
0.10.8
    Avoid compilation warnings on GHC 7.8
    #9, add --numeric-version flag
    Update the copyright year
    Change GetOpt.usageInfo to be more like GetOpt
   2014-05-22 23:39:23 by Ryosuke Moro | Files touched by this commit (5)
Log message:
Import cmdargs-0.10.7 as devel/hs-cmdargs,
packaged for wip.

This library provides an easy way to define command line parsers.
Most users will want to use the System.Console.CmdArgs.Implicit module,
whose documentation contains an example.

* System.Console.CmdArgs.Explicit provides a way to write command line parsers
  for both single mode programs (most programs) and multiple mode programs
  (e.g. darcs or cabal). Parsers are defined by constructing a data structure.

* System.Console.CmdArgs.Implicit provides a way to concisely define
  command line parsers, up to three times shorter than getopt.
  These parsers are translated into the Explicit data type.

* System.Console.CmdArgs.GetOpt provides a wrapper allowing compatiblity
  with existing getopt parsers, mapping to the Explicit data type.

For a general reference on what command line flags are commonly used,
see http://www.faqs.org/docs/artu/ch10s05.html.