Decimal Significant Digit Count
Count spelling-defined significant digits with an explicit integer-trailing-zero policy; decimal trailing zeros count and all-zero text counts as one.
Description
Count spelling-defined significant digits with an explicit integer-trailing-zero policy; decimal trailing zeros count and all-zero text counts as one.
Significant-digit counts depend partly on whether integer trailing zeros are considered meaningful. Exponent spelling does not add coefficient digits.
When to use this tool
Count spelling-defined significant digits with an explicit integer-trailing-zero policy; decimal trailing zeros count and all-zero text counts as one.
- Prepare the supplied decimal, integerTrailingZerosSignificant 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
- Enter decimal, integerTrailingZerosSignificant. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.significantDigits, result.zero. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Validate the exact decimal spelling, concatenate mantissa digits and remove leading zeros. If no decimal point is present and integerTrailingZerosSignificant is false, also remove trailing zeros. Return remaining count or one for zero, plus a zero flag.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| decimal | decimal. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| integerTrailingZerosSignificant | Explicit choice for integer trailing zeros significant; supply a boolean rather than a text label. | true or false |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.significantDigits | Count under the explicit spelling and integer-trailing-zero policy, with one for zero. |
| result.zero | Flag for zero under the exact condition described above. |
{
"input": {
"decimal": "0.001200",
"integerTrailingZerosSignificant": false
},
"output": {
"result": {
"significantDigits": 4,
"zero": false
}
}
}Limitations and assumptions
- This is an explicit spelling policy rather than an inferred measurement precision. A zero mantissa counts as one even if several decimal zeros were written.
- Exact decimal-spelling operations require digits before the optional decimal point and allow a signed exponent. Decimal text is bounded to 256 code units and effective scale to minus 256 through 256; integer-string fields allow a sign and up to 256 digits.
- 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.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- 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
Preserve decimal and integer strings when exact comparisons matter. Select signedness, scale, rounding and overflow policies separately, and use the matching encoder/decoder rather than a floating-point approximation.
References
Similar or alternative tools
- Decimal Negative Zero Policy
Apply an explicit negative-zero spelling policy without treating negative zero as a different numerical value.
- Decimal Quantum Membership
Exact decimal quantum membership; signed arithmetic uses floor rather than truncation.