Timestamp Millisecond Component Join
Join exact signed epoch second text and a 0–999 millisecond component without unsafe numeric conversion.
Description
Join exact signed epoch second text and a 0–999 millisecond component without unsafe numeric conversion.
A floor-based second count plus a nonnegative millisecond remainder can represent negative timestamps consistently.
When to use this tool
Join exact signed epoch second text and a 0–999 millisecond component without unsafe numeric conversion.
- Prepare the supplied seconds, millisecond 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 seconds, millisecond. 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.milliseconds. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse seconds as exact integer text and require millisecond from 0 to 999. Return seconds*1000+millisecond as decimal integer text.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| seconds | Exact decimal integer text; keep it quoted in JSON rather than converting through a floating-point number. | Optional leading + or - and 1 to 256 decimal digits; no whitespace |
| millisecond | millisecond. | Integer from 0 to 999 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.milliseconds | The milliseconds value under the stated formula or text convention. |
{
"input": {
"seconds": "-1",
"millisecond": 999
},
"output": {
"result": {
"milliseconds": "-1"
}
}
}Limitations and assumptions
- The remainder is not a separately signed fraction. No epoch, timezone or leap-second policy is supplied.
- 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
Keep elapsed durations, circular clocks, calendar months and epoch offsets distinct. Use a date/time method with explicit timezone and timescale rules for dated instants; arithmetic on one representation does not supply the others.
References
Similar or alternative tools
- Timestamp Second Millisecond Split
Split an exact signed epoch millisecond integer into floor seconds and a nonnegative millisecond component.
- Duration Component Normalizer
Normalize signed fixed-day duration components by floor division into a signed day count plus nonnegative subday components.