(Unicode C) Demonstrates how to Handle Large Integers in JSON

See more JSON Examples

Demonstrates how to handle large integers in JSON. (Integers larger than what can fit in a 32-bit signed integer.)

Chilkat C/C++ Library Downloads
MS Visual C/C++ Linux/CentOS C/C++ Alpine Linux C/C++ MAC OS X C/C++	armhf/aarch64 C/C++ C++ Builder iOS C/C++ Android C/C++	Solaris C/C++ MinGW C/C++

#include <C_CkJsonObjectW.h>

void ChilkatSample(void)
    {
    HCkJsonObjectW json;
    BOOL success;
    int id;
    const wchar_t *accountId;

    // Let's say your JSON has this:

    // {
    // 	"id": 20000000001234567
    // }

    json = CkJsonObjectW_Create();

    success = CkJsonObjectW_LoadFile(json,L"qa_data/json/large_int.json");
    if (success == FALSE) {
        wprintf(L"%s\n",CkJsonObjectW_lastErrorText(json));
        CkJsonObjectW_Dispose(json);
        return;
    }

    // The integer is too large for a 32-bit signed integer that is returned by IntOf.
    // The result will be something that wrapped around and could be negative.
    // In this case it would be: -543893881
    id = CkJsonObjectW_IntOf(json,L"id");
    wprintf(L"id: %d\n",id);

    // The solution is to read the integer value as a string, and then use the features in your programming language
    // to convert from a string to a 64-bit integer.
    // 
    // Alternatively, you may wish to simply hold the value as a string.  If, for example, the integer simply references
    // an order ID, an account ID, etc., then there's no need to convert to an integer value.  You're not going to be doing
    // mathematical operations on it anyway.  This is usually the case for large integers -- they typically exist
    // in JSON as an account ID.

    // You can get any JSON value as a string:
    accountId = CkJsonObjectW_stringOf(json,L"id");
    wprintf(L"accountId: %s\n",accountId);

    // Sample output:

    // id: -543893881
    // accountId: 20000000001234567


    CkJsonObjectW_Dispose(json);

    }