| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Only our documentation claims that any of the JSON code throws
NumberFormatException, and throwing JSONException seems much more in keeping
with the rest of the API (and makes it easier for callers to handle errors).
Bug: https://code.google.com/p/android/issues/detail?id=103641
Change-Id: I4f4ebfd983f4ccb2a1f266a0bfa5732174df26f6
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also, add type arguments to the old Iterator API.
Note that this is source incompatible with wrongly generified
code (example: "Iterator<Object> keys = jsonObject.keys();") but
is compatible with old code that didn't use any type arguments.
Users compiling against the new SDK might see compile breakages.
bug: https://code.google.com/p/android/issues/detail?id=63191
Change-Id: Idf2ef1889dccb4309c843ab073f67af648b09436
|
|
|
|
|
|
| |
Javadoc referred to a hidden method via a {@link} tag.
Change-Id: I18fc8a05aacd17bdc5fffe4f08870aa3d6d47b93
|
|
|
|
|
|
|
|
| |
It provides better semantics that accumulate. In particular,
the type of the mapping does not depend on the number of calls
to the function.
Change-Id: Ib8f9d229d8de72d57b25ff9d69c69a61215c2fd7
|
|
|
|
|
|
|
|
| |
Changed the map type in JSONObject to a LinkedHashMap so that
its iteration order is well defined.
bug: 12476022
Change-Id: I8f2e40fd6bca5f776396aba4c9fde6e9d58f662e
|
|
|
|
|
|
|
|
|
| |
The class documentation makes the difference between the 'get' and 'opt'
methods very clear, but it's less clear to anyone just looking at the
summary of methods.
Bug: https://code.google.com/p/android/issues/detail?id=60998
Change-Id: I17eeaea182a9dbad7be9fbd55086977b512b6fa8
|
|
|
|
|
| |
Bug: https://code.google.com/p/android/issues/detail?id=55114
Change-Id: Ic2e010ac616f24dda7b8abced7eb2fc84dc7d50e
|
|
|
|
|
| |
Bug: https://code.google.com/p/android/issues/detail?id=53461
Change-Id: I2b920fa8d63bcc8f1260669d72e33833bbd81ced
|
|
|
|
|
| |
Bug: https://code.google.com/p/android/issues/detail?id=47878
Change-Id: I0cd05348708a2374a0e301f778bc2ed29cc38f94
|
|
|
|
|
|
| |
I've left java.util.concurrent alone, since that's upstream code.
Change-Id: I349960aaddb78e55d4c336b58b637009db69ff98
|
|
|
|
|
| |
Bug: http://code.google.com/p/android/issues/detail?id=18508
Change-Id: Ib992a0a4b22e340446abab14e4f32df5efcd0b49
|
|
|
|
|
|
|
|
|
|
| |
When we reimplemented this API I broke consistency with
org.json. Bringing it back into line makes the implementation
more strict (my preference) and makes us consistent with
ourselves before this code was redone.
Bug: http://code.google.com/p/android/issues/detail?id=16411
Change-Id: I8c1b52e382ad91932d3cf9a5b346db58df4da7c6
|
|
|
|
| |
Change-Id: Ie9dde4971e0a6a8dadd14af43d631158fc488cd8
|
|
|
|
| |
Change-Id: I8347bc625480a1c37a1ed9976193ddfedeb00bbc
|
|
|
|
|
|
|
|
|
|
| |
Neither the JSON RFC nor the documentation of Crockford's
implementation mention these comments, but somehow the
old parser used to support these. And so we shall also.
See bug 2571423.
Change-Id: I77d64c5ec53278d8df5fe1873404f1241320504b
|
|
|
|
|
|
|
|
|
|
| |
Our behaviour is consistent with Crockford's.
The test confirms that the behaviour is consistent with the report
of that bug, which the submitter claims is not how it should behave.
http://code.google.com/p/android/issues/detail?id=7257
Change-Id: Ibace4bd995e3cbc8fb6c9dc509f8f4491865a647
|
|
|
|
|
|
|
| |
Although this violates my longstanding style preference, it agrees
with almighty JJB's official ArrayList, which is Good Enough For Me.
Change-Id: I7b608c12e04d0b7789bfcabeab4b7347ad22baca
|
|
|
|
| |
Change-Id: I3aced2607b48210f76887e0d42b591c098ce5db7
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I5ec9df6a3a9baac8f4f498890cd35feff774737a
|
|/
|
|
| |
Change-Id: I9837cfd46684ac6d5b9ec4ac6809da3c3f61d57d
|
|
|
|
| |
Change-Id: I277ec3b35a28802dd7b7f82c1f4bbadbd3cc4c65
|
|
|
|
| |
Change-Id: I1b67bac70bd25220a619e6ebe61f7f1c6f316faa
|
|
|
|
| |
Change-Id: Ife53082824f5916665f198d4b2fb863271841ce0
|
| |
|
| |
|
|
|