add flag to drop the limit of json depth

[shoothzj]

No description provided.

[UrielCh]

the default parser flag should be 0
the limit should be enabled by default.
the flag name should be called:
UNLIMITED_JSON_DEPTH and do the opposite.

[UrielCh]

why FINITE_JSON_DEPTH could not benefit of an import static wherever DEFAULT_PERMISSIVE_MODE can.

[UrielCh]

DEFAULT_PERMISSIVE_MODE & ~FINITE_JSON_DEPTH ?
should be:
DEFAULT_PERMISSIVE_MODE | FINITE_JSON_DEPTH ?

[UrielCh]

I do not remember this code, but I think that the default parser value is 0
...
So the issue is that the flag should be call UNLIMITED_JSON_DEPTH and do the opposite.
The limit is enabled by default for now, and can be disabled in some rare cases.

[UrielCh]

to the fixed version should be: DEFAULT_PERMISSIVE_MODE | UNLIMITED_JSON_DEPTH

[UrielCh]

after reading the code:

	/**
	 * smart mode, fastest parsing mode. accept lots of non standard json syntax
	 * 
	 * @since 1.0.6
	 */
	public final static int MODE_PERMISSIVE = -1;

The MODE_PERMISSIVE is the mode I use by default for my stuff.

	/**
	 * Default json-smart processing mode
	 */
	public static int DEFAULT_PERMISSIVE_MODE = (System.getProperty("JSON_SMART_SIMPLE") != null) ? MODE_JSON_SIMPLE
			: MODE_PERMISSIVE;

what...
I do not remember....

what is the default mode ?
the default mode should keep the limit.

[UrielCh]

I remember my way of codding.
The ~ tild operator should be avoid. Check the rest of the code I did not used any of them.

[shoothzj]

@UrielCh I agree with that the limited ability should be enabled by default. But the default value is -1, not 0.

[UrielCh]

Change the since.
bump the version number and that should be done,

bump minor or patch ?
since you add a new flag that a minor upgrade. so change the second digit, and set the third one to 0.

[UrielCh]

so the next version is V 2.5.0

[shoothzj]

@UrielCh I have done bump the minor versions. But I think we can't avoid using ~ since the default mode is -1.