67a3028555
JSON famously is problematic with integers beyond 53 bits, because JavaScript stores everything in double precision floating points. Various implementations in other languages can deal with signed 64 bit integers, and a few can deal with unsigned 64bit too (like ours). Typically program that need more then 53 bit of accuracy encode integers as decimal strings, to make sure that even if consumers can't really process larger values they at least won't corrupt the data while passing it along. This is also recommended by JSON-I (RFC 7493) To maximize compatibility with other implementations let's add 1st class parsing support for such objects in the json_dispatch() API. This makes json_dispatch_uint64() and related calls parse such integers-formatted-as-decimal-strings as uint64_t. This logic will only be enabled if the "type" field of JsonDispatch is left unspecified (i.e. set to negative/_JSON_VARIANT_TYPE_INVALID) though, hence alone does not change anything in effect. This purely is about consuming such values, whether we should genreate them also is a discussion for a separate PR.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.