Added object methods for methods returning primitives

[davejbur]

Added object methods for:

• optBooleanObj (returns Boolean vice boolean)
• optFloatObj (returns Float vice float)
• optIntegerObj (returns Integer vice integer)
• optLongObj (returns Long vice long)

The reason for doing so is that, sometimes, I want (e.g.) optInt to return null if a value isn't found (i.e. I want to do optInt(theKey,null)). However, that gives a compiler error <null> cannot be converted to int, since optInt needs to return an int. Hence adding an almost identical function that returns an Integer instead.

(I've finally worked out why, in a previous attempt at doing this, Github was trying to allege I'd changed the whole file...! GH was changing all the line endings for me instead of just leaving well alone.)

[stleary]

@davejbur Thanks for the pull request, this seems like a reasonable change.

• Would you mind changing 'Obj' to 'Object', e.g. optFloatObject()?
• When adding an API method to JSONObject, please add the corresponding method in JSONArray.
• Please add unit tests for new methods.

[javadev]

I suggest these method names

getOptionalBooleanObject()
getOptionalFloatObject()
getOptionalIntegerObject()
getOptionalLongObject()

[spaffrath]

@davejbur Can't this be done using the current API with optInt("x", (Integer) null) and so on?

[stleary]

I believe optInt("x", (Integer) null) will throw a NullPointerException because the 2nd param is a primitive int.
But this code could work:

Integer i = null;
if (j.has("a")) {
    i = j.getInt("a");
}

[spaffrath]

@stleary Yes, of course 👍

[davejbur]

I suggest these method names

getOptionalBooleanObject()
getOptionalFloatObject()
getOptionalIntegerObject()
getOptionalLongObject()

Thanks - I was trying to keep in line with the optBoolean etc naming convention already in use.

[davejbur]

Closing this as now dealt with by #753.