History log of /libcore/xml/src/main/java/org/xmlpull/v1/XmlPullParser.java
Revision Date Author Comments
de7e8c4314e6954f4f5996f9929dc9db81d500a9 06-Jul-2015 Narayan Kamath <narayan@google.com> Fix typo in javadoc.

"mus" -> "must"

bug: https://code.google.com/p/android/issues/detail?id=178755
Change-Id: Ie418de27cc664597cc54f7c2a4395621bea0dc60
c9b4e40b19fdf79c22d4774600f704b473f47067 12-Dec-2013 Elliott Hughes <enh@google.com> Fix a javadoc typo.

Bug: https://code.google.com/p/android/issues/detail?id=62919
Change-Id: Iadb85c25ec7e07ee245b009f5fb848c8228924a1
f1a7fc1453676af318ce11fed9616cbb090b83ae 10-May-2012 Jesse Wilson <jessewilson@google.com> Use weasel words to cover changed behavior around END_DOCUMENT.

We used to have 2 different implementations of XmlPullParser and
each of them behaved differently if you called next() after
receiving the END_DOCUMENT token:
- Parsers returned from XmlPullParserFactory didn't throw
- Parsers returned from android.util.Xml did throw

When we went to a single implementation the behavior changed for
android.util.Xml users. Unfortunately the change went from being
consistent-with-the-docs to not. Rather than changing the behavior
I'm being a weasel and changing the docs! That way we aren't
promising something we cannot deliver.

Bug: http://code.google.com/p/android/issues/detail?id=29931
Change-Id: I0e72e79270b92ecc0fdb5bf64c97fa50d2bdb81c
59aa66320912bdb09c740d2f515bc8da5c5d27b1 18-Apr-2012 Elliott Hughes <enh@google.com> Fix a minor documentation bug in XmlPullParser.

Bug: http://code.google.com/p/android/issues/detail?id=29028
Change-Id: I25464730869499369fb7ec8e282ba5c67ebe909f
48d7dbad8dd83395667d9846e49c5ba38f0a5258 11-Nov-2011 Jesse Wilson <jessewilson@google.com> Warn about a fixed bug in XmlPullParser.nextText()

Bug: http://code.google.com/p/android/issues/detail?id=21425
Change-Id: I4c69d67bb8bfdf3f78359d800860d5dc2e2e349f
786a6ea948f312a9fc1962659150319cb0ce9e71 14-Nov-2010 Jesse Wilson <jessewilson@google.com> Fix a typo in the XmlPullParser example.

Originally reported here:
http://groups.google.com/group/android-platform/browse_thread/thread/6020aee5f01f21df/afac4ce1a0184788?show_docid=afac4ce1a0184788

Change-Id: I378a441117fdf41e74d91ba8fef8ac9abf5a5275
fda724de28fe86804e6ef6a0afd7ae5be1529083 05-Nov-2010 Jesse Wilson <jessewilson@google.com> Optimize KxmlParser.

I benchmarked this on four files:

size file
268 rhapsody authorization
29489 picasa sync (for gallery)
101129 amazon mp3 search results
103855 RSS feed

The performance regressed for the 268-byte file from 1.44ms to 1.56ms.
Small files are important and I intend to follow-up to bring this back
into line.

For the other files, the improvements for pull parsing were 22%, 34% and 29%.
Improvements for DOM parsing were 17%, 23% and 21%.

All but the 268-byte document now parse faster with Kxml than with Expat.

101129 byte amazon mp3 search results 29489 byte picasa sync dat 268 byte rhapsody authentication 103855 byte RSS feed
benchmark run us linear runtime us linear runtime us linear runtime us linear runtime
Dom ready to commit 174,580 ======================== 40,964 ======================= 1,968 =========================== 130,814 =======================
Dom baseline 210,256 ============================== 53,227 ============================== 2,183 ============================== 164,708 =============================
ExpatPull ready to commit 129,776 ================== 21,621 ============ 734 ========== 86,799 ===============
ExpatPull baseline 130,078 ================== 21,700 ============ 759 ========== 85,578 ===============
KxmlPull ready to commit 88,716 ============ 20,578 =========== 1,560 ===================== 58,567 ==========
KxmlPull baseline 114,317 ================ 31,040 ================= 1,443 =================== 82,478 ===============

Change-Id: I98b7f979c2f926e25c72541bf9f5036f097e8d91
http://b/3090550
ccd79e2bb784cdbd89e90a0e4301a707091d446d 04-Nov-2010 Jesse Wilson <jessewilson@google.com> Style cleanup of some XML code.

Motivation: in preparation to refactor the Kxml code I'd like
to bring this code to a style consistent with the rest of
Android. This code style currently disagrees with my toolchain.

Change-Id: Ibd24570c131e792532e46f7f44c64abac3a6979a
http://b/3090550
87806e1dba84c281567b6d1bb9bb61f3e95ab744 12-Nov-2009 Elliott Hughes <enh@google.com> Fix typos in the XmlPullParser documentation.
adc854b798c1cfe3bfd4c27d68d5cee38ca617da 04-Mar-2009 The Android Open Source Project <initial-contribution@android.com> auto import from //depot/cupcake/@135843
1c0fed63c71ddb230f3b304aac12caffbedf2f21 04-Mar-2009 The Android Open Source Project <initial-contribution@android.com> auto import from //depot/cupcake/@135843
fdb2704414a9ed92394ada0d1395e4db86889465 21-Oct-2008 The Android Open Source Project <initial-contribution@android.com> Initial Contribution