Android™

JSON UpdateNumber vs UpdateInt

Demonstrates UpdateNumber vs UpdateString. Android™

// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;

import android.app.Activity;
import com.chilkatsoft.*;

import android.widget.TextView;
import android.os.Bundle;

public class SimpleActivity extends Activity {

  private static final String TAG = "Chilkat";

  // Called when the activity is first created.
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    CkJsonObject json = new CkJsonObject();

    //  If a number is too large for a 32-bit signed integer, then call UpdateNumber instead of UpdateInt.
    //  The large integer is passed to UpdateNumber as a string, but in the JSON it will be an integer.

    //  For example:
    json.UpdateNumber("largeNumber","6884556842");

    //  If the integer is small enough for a 32-bit signed integer, then use UpdateInt:
    json.UpdateInt("reasonableInt",123456);

    json.put_EmitCompact(false);
    Log.i(TAG, json.emit());

    //  The output:
    //  Notice the large number passed as a string does not have quotes in the JSON

    //  {
    //    "largeNumber": 6884556842,
    //    "reasonableInt": 123456
    //  }

  }

  static {
      System.loadLibrary("chilkat");

      // Note: If the incorrect library name is passed to System.loadLibrary,
      // then you will see the following error message at application startup:
      //"The application <your-application-name> has stopped unexpectedly. Please try again."
  }
}