Decimal Negative Zero Policy
Apply an explicit negative-zero spelling policy without treating negative zero as a different numerical value.
Description
Apply an explicit negative-zero spelling policy without treating negative zero as a different numerical value.
Decimal negative zero can carry a formatting distinction even though its exact rational value is zero.
When to use this tool
Apply an explicit negative-zero spelling policy without treating negative zero as a different numerical value.
- Prepare the supplied decimal, preserve 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, preserve. 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.decimal, result.wasNegativeZero. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse decimal into integer coefficient, effective scale and a negative-zero marker. Expand its spelling; retain a leading minus on zero only when preserve is true. Return wasNegativeZero independently.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| decimal | decimal. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| preserve | Explicit choice for preserve; supply a boolean rather than a text label. | true or false |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.decimal | The decimal value under the stated formula or text convention. |
| result.wasNegativeZero | Whether the original decimal spelling denoted a negative zero, independently of output policy. |
{
"input": {
"decimal": "-0.00",
"preserve": true
},
"output": {
"result": {
"decimal": "-0.00",
"wasNegativeZero": true
}
}
}Limitations and assumptions
- Scale is preserved by the expansion policy, but exponent notation and explicit plus signs are not. This does not emulate every floating-point signed-zero operation.
- 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 Spelling Zero Trimmer
Canonicalize a decimal spelling by removing fractional trailing zeros and integer leading zeros; negative zero becomes zero.
- Decimal Quantum Membership
Exact decimal quantum membership; signed arithmetic uses floor rather than truncation.