[Teem-commit] SF.net SVN: teem:[7495] teem/trunk/src/hest/README. md

[<kin...@us...>]

Revision: 7495
          http://sourceforge.net/p/teem/code/7495
Author:   kindlmann
Date:     2025-09-26 11:31:55 +0000 (Fri, 26 Sep 2025)
Log Message:
-----------
tweaking

Modified Paths:
--------------
    teem/trunk/src/hest/README.md

Modified: teem/trunk/src/hest/README.md
===================================================================
--- teem/trunk/src/hest/README.md	2025-09-25 21:55:39 UTC (rev 7494)
+++ teem/trunk/src/hest/README.md	2025-09-26 11:31:55 UTC (rev 7495)
@@ -58,7 +58,7 @@
     min >    0              1              2
 ```
 
-The `kind` of option is mostly independent of whether it is flagged or unflagged, and independent of being optional (due to the `hestOpt` having a default string) versus required (when no default is given). The one wrinkle is that unflagged options must have at least one parameter (i.e. `min` > 0), either by the command-line or via a default string. An unflagged option allowed to have zero parameters has no explicit textual existence, which seems out-of-bounds for a command-line parser. Thus for unflagged options, `kind`s 1 and 4 are ruled out, and kind 5 is possible with `min` >= 1. This is likely already too much low-level information: users of `hest` will probably never need to worry about `kind`, and certainly `kind` is not part of the API calls to create options and parse command-lines.
+The `kind` of option is mostly independent of whether it is flagged or unflagged, and independent of being optional (due to the `hestOpt` having a default string) versus required (when no default is given). The one wrinkle is that unflagged options must have at least one parameter (i.e. `min` > 0), either by the command-line or via a default string. An unflagged option allowed to have zero parameters has no explicit textual existence, which seems out-of-bounds for a command-line parser. Thus for unflagged options, `kind`s 1 and 4 are ruled out, and kind 5 is possible only with `min` >= 1. This is likely already too much low-level information: users of `hest` will probably never need to worry about `kind`, and certainly `kind` is not part of the API calls to create options and parse command-lines.
 
 Some **concrete examples** may be helpful for understanding `hest`'s utility ... (IN PROGRESS) ...
 ... Give some specific examples, flagged and unflagged ...

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.