Numbered Filename Suffix Parser

Parse a terminal parenthesized unsigned decimal filename suffix before a parentheses-free extension tail; preserve digit width and exact decimal value.

Description

Parse a terminal parenthesized unsigned decimal filename suffix before a parentheses-free extension tail; preserve digit width and exact decimal value.

A parenthesized decimal suffix can expose both its numeric value and its original digit width.

When to use this tool

Parse a terminal parenthesized unsigned decimal filename suffix before a parentheses-free extension tail; preserve digit width and exact decimal value.

  • Prepare the supplied name fields for this operation.
  • Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

  1. Enter name. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.matched, result.prefix, result.numberDecimal, result.digitWidth, result.suffix. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Validate name and match the final qualifying parenthesized digit group with a following suffix containing no parentheses. Return matched plus prefix, canonical numberDecimal, original digitWidth and suffix, or null fields if unmatched.1

Input fieldMeaning and representationAccepted input
namename.Text; at most 8,192 UTF-16 code units, subject to the grammar above
Output fieldInterpretation
resultObject containing the named outputs below.
result.matchedFlag for matched under the exact condition described above.
result.prefixThe prefix value under the stated formula or text convention.
result.numberDecimalThe number decimal value under the stated formula or text convention.
result.digitWidthThe digit width value under the stated formula or text convention.
result.suffixThe suffix value under the stated formula or text convention.
json
{
  "input": {
    "name": "report(007).txt"
  },
  "output": {
    "result": {
      "matched": true,
      "prefix": "report",
      "numberDecimal": "7",
      "digitWidth": 3,
      "suffix": ".txt"
    }
  }
}

Limitations and assumptions

  • No number is converted through floating point. This recognizes its stated pattern, not every numbered-filename convention, and no rename occurs.
  • Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
  • String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. Nonfinite results and excessively large serialized outputs are rejected.
  • Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Use a filesystem-aware implementation with appropriate platform semantics for actual file operations. Literal slash components, Unicode comparison and filename plans do not resolve symlinks or atomically reserve a destination.

References

  1. Tool behavior and example: Numbered Filename Suffix Parser — tool.io

Similar or alternative tools

  • Numbered Filename Suffix Formatter

    Format a parenthesized unsigned decimal filename suffix with minimum digit width; exact decimal text avoids unsafe numeric conversion.

  • Filename Casefold Collision Table

    Audit the bounded ASCII case-insensitive filename branch; rejects non-ASCII rather than pretend lowercasing implements full Unicode case folding.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies