diff options
| author | Jesse Wilson <jessewilson@google.com> | 2012-05-10 15:48:12 -0400 |
|---|---|---|
| committer | Jesse Wilson <jessewilson@google.com> | 2012-05-10 16:36:14 -0400 |
| commit | f1a7fc1453676af318ce11fed9616cbb090b83ae (patch) | |
| tree | 9ccaf30ec22e81f82a84fd2e480ed06d3093bdb2 /annotations/generate_annotated_java_files.py | |
| parent | d71c8470c187ac3bcd1bcba055bc0389da4eec98 (diff) | |
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
Diffstat (limited to 'annotations/generate_annotated_java_files.py')
0 files changed, 0 insertions, 0 deletions