History log of /external/libxml2/libxml2.syms
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
f4e5a6994ed230dfa3fb5b5c3fd94c4993ef1ba7 19-Apr-2013 Daniel Veillard <veillard@redhat.com> Release of libxml2-2.9.1

* configure.in: bumped version
* doc/*: updated the symbols file and regenerated
/external/libxml2/libxml2.syms
38bbd3412d1c2a2016cf5a1a221ad4010216d28e 11-Sep-2012 Daniel Veillard <veillard@redhat.com> Release of libxml2-2.9.0

* libxml.spec.in: update
* doc/*: updated and regenerated
* libxml2.syms testapi.c: regenerated
/external/libxml2/libxml2.syms
82cdfc4eb338f039024e1619aca8ff14b5c3dc71 22-Aug-2012 Daniel Veillard <veillard@redhat.com> Expose xmlBufShrink in the public tree API

As suggested by Andrew W. Nosenko:
Proposal: expose the new xmlBufShrink() to the "public" API for
compatibility with xmlBufUse().

Reason: the following scenario:

1. Read something into xmlParserInputBuffer (e.g. using
xmlParserInputBufferRead())
2. Extract content through xmlBufContent()
3. Extract content length through xmlBufUse(). Result have type
'size_t'.
4. Use this content
5. Now, you need to shrink the buffer. How to do it? Doing that
through legacy xmlBufferShrink() is unsafe because it uses 'unsigned
int' and the whole point of introducing the new API was handling the
cases, when 'unsigned int' is not enough. Therefore, need to use the
new xmlBufShrink(). But it is "private".

Therefore, I propose to expose the new xmlBufShrink() in the same way,
as xmlBufContent() and xmlBufUse() are exposed.
/external/libxml2/libxml2.syms
64d11249a51c1a10e87b51bc1fa633d4605d483e 15-Aug-2012 Daniel Veillard <veillard@redhat.com> Fix missing xmlsave.h module which was ignored in recent builds

due to "save.h" rule discarding it too
/external/libxml2/libxml2.syms
ee8f1d4cda8dc1a6f2c515fe234f7bc89cdc9f80 21-May-2012 Daniel Veillard <veillard@redhat.com> Cleanups before 2.8.0-rc2

new symbols, a missing comment and a fix on symbol release
/external/libxml2/libxml2.syms
f27c6683e6a8a5ed168ee24f0c114af7b7dc82fa 21-May-2012 Daniel Veillard <veillard@redhat.com> New symbols added for the next release
/external/libxml2/libxml2.syms
f447ab8f97830c06f24eb589ecaabc69001e3e78 24-Aug-2009 Daniel Veillard <veillard@redhat.com> Regenerated API and symbols

* doc/Makefile.am: make the check for symbols pbm a make api failure
* doc/symbols.xml: added xmlXIncludeProcessTreeFlagsData
* doc//* elfgcchack.h libxml2.syms testapi.c: regenerated
/external/libxml2/libxml2.syms
472b1e115012c92144c073efc6c284e72ff297bf 24-Aug-2009 Daniel Veillard <veillard@redhat.com> Regenerate symbols and API after previous patches

* doc/symbols.xml: new global data xmlStructuredErrorContext
* doc/checkapisym.xsl: slightly improve output
* doc/* libxml2.syms win32/libxml2.def.src: regenerated the API
/external/libxml2/libxml2.syms
f609d745b15d16ddc6a951ebcf4431a98e27dfc4 21-Aug-2009 Daniel Veillard <veillard@redhat.com> Autoregenerate libxml2.syms automated checkings

* doc/symbols.xml: the source for all exported symbols
* doc/checkapisym.xsl: used to check libxml2-api.xml against exported
symbols
* doc/syms.xsl: stylesheet regenerating libxml2.syms from symbols.xml
* doc/Makefile.am libxml2.syms: add the new rules and the generated
version
/external/libxml2/libxml2.syms
8ed1072c2d4dac0bc72a8d0ebff7ccc1b338f035 20-Aug-2009 Daniel Veillard <veillard@redhat.com> Add symbol versioning to libxml2 shared libs

* libxml2.syms: the symbols with history, going back to 2.4.30
* Makefile.am configure.in: linking flags detection and use
* parser.c tree.c valid.c xpointer.c: various cleanup of functions
which could be made static or simply discarded, not that many
/external/libxml2/libxml2.syms