Description
Audit empty INI section occurrences by explicit occurrence-index assignment ownership, distinguishing repeated section headings with the same name.
INI-like configuration formats vary between applications. In this tool family, assignments are explicit section/name/value records and the empty section string means global scope. Duplicate-key policies, case handling and preservation of comments are separate choices rather than one universal INI behavior.
Audit empty INI section occurrences by explicit occurrence-index assignment ownership, distinguishing repeated section headings with the same name.
When to use this tool
Use this tool to audit empty INI section occurrences by explicit occurrence-index assignment ownership, distinguishing repeated section headings with the same name.
How to use the tool and how it works
- Enter sections, assignmentSectionIndexes using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.emptyOccurrenceIndexes. Use the ordering, boundary rules and absence conditions described below.
Validate section occurrences and assignmentSectionIndexes, then return occurrence positions referenced by no assignment.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sections | Explicit section-occurrence labels, in occurrence order. | Dense list of at most 128 strings, each at most 8,192 UTF-16 code units. |
| assignmentSectionIndexes | Zero-based indexes of section occurrences that have assignments. | Dense list of at most 128 finite numbers; integer/shape constraints above also apply. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.emptyOccurrenceIndexes | Section-occurrence positions referenced by no assignment. |
{
"input": {
"sections": [
"a",
"a",
"b"
],
"assignmentSectionIndexes": [
1
]
},
"output": {
"result": {
"emptyOccurrenceIndexes": [
0,
2
]
}
}
}Limitations and assumptions
- Separate occurrences with the same section name are distinct; only supplied occurrence indexes determine emptiness.
- Assignment records contain section, name and value strings. Nonempty section/key names cannot have surrounding whitespace, brackets or CR/LF/NUL. Values cannot contain CR/LF/NUL; a key cannot contain equals. No implicit interpolation or typed-value conversion is performed.
- Every declared top-level input field is required and unexpected 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 no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Select the consuming application’s dialect and duplicate-key policy explicitly. Use a lossless configuration editor when comments, original spacing, quoting or application-specific interpolation must be preserved.
References
Similar or alternative tools
- INI Section Occurrence Grouping
Group adjacent supplied INI section labels into distinct occurrence runs, preserving later returns to the same name rather than globally merging sections.
- INI Global Key Section Partition
Partition explicit INI key observations between the unsectioned global namespace and named sections; preserves original records, duplicates and empty values.