Description
Expand one bounded cron wildcard/range step field with inclusive bounds; excludes lists, names, wrap ranges and day-of-week aliases.
Parsing depends on the chosen grammar, character encoding, offset unit, and treatment of escapes and delimiters. UTF-16 code-unit positions, Unicode code points, and UTF-8 byte offsets are not interchangeable. A boundary or token check supplies one part of a parser rather than validating an entire file.
Expand one bounded cron wildcard/range step field with inclusive bounds; excludes lists, names, wrap ranges and day-of-week aliases.
When to use this tool
Use Parsing: Crontab Step Single Field when you need the stated token boundary, offset, prefix, delimiter, or count component inside a larger parsing workflow.
How to use the tool and how it works
- Enter field, minimum, maximum. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
For integer minimum in [0,1000] and maximum from minimum through minimum+127 accept field=*/step or start-end/step with 1-4-digit tokens and step in [1,1000]. Validate the range within the supplied bounds and return inclusive arithmetic-progression values inside result.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| field | Field | Required. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. |
| minimum | Minimum | Required. Safe integer. |
| maximum | Maximum | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Object containing the calculated result members described below. | Required. Object. |
| result.values | Values | Calculated result member: array. |
{
"input": {
"field": "1-7/2",
"minimum": 0,
"maximum": 9
},
"output": {
"result": {
"values": [
1,
3,
5,
7
]
}
}
}Limitations and assumptions
- This expands one bounded field only. Lists, named months/days, plain values, wraparound ranges, time zones, day-field interaction, and actual job scheduling are unsupported.
- Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.
Alternative or Complementary methods
Choose a parser for the intended complete grammar when context, nesting, encodings, or semantic validation matters. Keep byte, code-unit, and code-point coordinates explicit when combining results.
References
Similar or alternative tools
- Token Lookahead Span
For nonnegative integer tokenCount and lookaheadCount and currentIndex within zero through tokenCount return endExclusive=min(tokenCount,currentIndex+lookaheadCount) and available=min(tokenCount-currentIndex,lookaheadCount).
- Length Prefixed Token Boundary
Resolve one supplied length-prefix boundary in a single caller-defined indexing unit.