Skip to content

Releases: eriknyquist/duckargs

v1.5.1

11 Aug 02:16
18a843d

Choose a tag to compare

Fix "argc" check in generated C code-- should match the number of positional arguments. If there are 3 positional arguments, for example, then the check should be "if (argc < 4)", and if there are no positional arguments, the check should be omitted entirely.

v1.5.0

05 Nov 18:51

Choose a tag to compare

  • Fix issues that cause broken python/C programs to be generated when language keywords are used as option names (e.g. "duckargs -i --int")
  • Ensure that NULL pointers are not passed to printf in generated C code
  • Fix unnecessary trailing "optind++" in generated C code
  • Minor improvements in "usage" printout in generated C code

Full Changelog: v1.4.0...v1.5.0

v1.4.0

22 Oct 21:42

Choose a tag to compare

  • Add support for generating C code

Full Changelog: v1.3.0...v1.4.0

v1.3.0

13 Oct 05:23

Choose a tag to compare

  • Add CLI script to setup.py, so 'duckargs' can be called directly (i.e. 'duckargs' instead of 'python -m duckargs')
  • Populate ArgumentParser 'description' field in generated programs
  • Recognize hex values and negative values as ints
  • Fix bugs when positional arg is a float/int
  • Add DUCKARGS_COMMENT and DUCKARGS_PRINT environment variables

Full Changelog: v1.2.0...v1.3.0

v1.2.0

11 Oct 07:04

Choose a tag to compare

  • Improve filename handling a bit (add FILE option argument)
  • Add usage printout on empty args

Full Changelog: v1.1.0...v1.2.0

v1.1.0

26 Mar 04:32

Choose a tag to compare

Bump version

v1.0.0

06 Mar 05:08

Choose a tag to compare

Bump version

v0.1.3

05 Mar 02:09

Choose a tag to compare

Bump version

v0.1.2

04 Mar 23:27

Choose a tag to compare

Fix README

v0.1.1

04 Mar 06:24

Choose a tag to compare

Bump version, add license