Skip to content

Main content

Option Positional Count Audit

Audit the already-partitioned positional argv count against explicit inclusive arity bounds; no option parsing.

Loading tool…

Description

Audit the already-partitioned positional argv count against explicit inclusive arity bounds; no option parsing.

An argv vector already consists of literal argument strings. Shell quoting and tokenization happen before this representation; joining argv elements with spaces does not reconstruct a safe command string. Option aliases, duplicates, arity and dependencies are application policies that these tools take explicitly.

Audit the already-partitioned positional argv count against explicit inclusive arity bounds; no option parsing.

When to use this tool

Use this tool to audit the already-partitioned positional argv count against explicit inclusive arity bounds; no option parsing.

How to use the tool and how it works

  1. Enter positionals, minimum, maximum using the input definitions below.
  2. Run the operation. Resolve malformed-input errors before interpreting the result.
  3. Read result.count, result.valid. Interpret signs, units, ordering and null values using the rules below.

Count the already-partitioned positional list and test minimum≤count≤maximum with integer arity bounds 0–128.1

Input fieldMeaning and unitsAccepted input
positionalsAlready-identified literal positional argument strings.Dense list of at most 128 strings, each at most 8,192 UTF-16 code units.
minimumInclusive minimum arity, integer 0–128.Finite safe integer satisfying the stated bounds.
maximumInclusive maximum arity, integer minimum–128.Finite safe integer satisfying the stated bounds.
Output fieldInterpretation
resultObject containing the fields below.
result.countSupplied positional argument count.
result.validWhether positional count lies within the explicit inclusive arity bounds.
json
{
  "input": {
    "positionals": [
      "a",
      "b"
    ],
    "minimum": 1,
    "maximum": 1
  },
  "output": {
    "result": {
      "count": 2,
      "valid": false
    }
  }
}

Limitations and assumptions

  • The tool does not parse options, find an end marker or decide which token is positional.
  • Inputs are literal tokens or explicit records. The restricted long-name grammar is [A-Za-z0-9][A-Za-z0-9-]* where required. No universal option syntax, shell semantics or process execution is inferred.
  • Every declared top-level input is required and unknown fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
  • Numeric outputs must be finite and within the absolute safe-integer magnitude; exact larger integers use decimal text. Source positions are zero-based UTF-16 offsets and span ends are exclusive unless a different convention is explicitly stated.

Alternative or Complementary methods

Use the application’s option schema to choose arity, aliases and conflict policy. Pass a literal argv vector to the intended process interface; shell command construction requires separate quoting rules.

References

  1. Tool behavior and example: Option Positional Count Audit — tool.io

Similar or alternative tools

  • Long Option Assignment Joiner

    Format one literal long-option argv token under a restricted ASCII option-name grammar; returns one argument, not shell quoting.

  • Long Option Assignment Splitter

    Split one strict ASCII --long-name[=value] argv token at the first equals; no shell parsing or implicit next-token consumption.