Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 1660331b | 2022-08-26 02:24:23 | Remove xmlErrMemory from symbols This function was never publically declared. | ||
| 34a050cd | 2022-08-24 16:35:58 | Move some HTML functions to correct header file | ||
| 9a82b94a | 2022-08-24 04:21:58 | Introduce xmlNewSAXParserCtxt and htmlNewSAXParserCtxt Add API functions to create a parser context with a custom SAX handler without having to mess with ctxt->sax manually. | ||
| 991a9fc2 | 2022-03-29 16:20:28 | Mark docbook symbols as removed | ||
| c2e09f44 | 2020-02-11 11:32:23 | Add xmlPopOutputCallbacks Add function to pop a single set of output callbacks from the stack. This was only implemented for input callbacks before. Fixes #135. | ||
| 80b110a9 | 2019-09-30 14:37:57 | Mark xmlExp* symbols as removed | ||
| 18890f47 | 2018-03-05 17:09:43 | Release of libxml2-2.9.8 * configure.ac doc/* libxml2.syms testapi.c: updated for the new release | ||
| f4e5a699 | 2013-04-19 15:36:36 | Release of libxml2-2.9.1 * configure.in: bumped version * doc/*: updated the symbols file and regenerated | ||
| 38bbd341 | 2012-09-11 15:00:08 | Release of libxml2-2.9.0 * libxml.spec.in: update * doc/*: updated and regenerated * libxml2.syms testapi.c: regenerated | ||
| 82cdfc4e | 2012-08-22 11:05:09 | 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. | ||
| 64d11249 | 2012-08-15 09:10:50 | Fix missing xmlsave.h module which was ignored in recent builds due to "save.h" rule discarding it too | ||
| ee8f1d4c | 2012-05-21 11:16:12 | Cleanups before 2.8.0-rc2 new symbols, a missing comment and a fix on symbol release | ||
| f27c6683 | 2012-05-21 10:15:40 | New symbols added for the next release | ||
| f447ab8f | 2009-08-24 19:47:00 | 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 | ||
| 472b1e11 | 2009-08-24 17:39:07 | 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 | ||
| f609d745 | 2009-08-21 15:16:46 | 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 | ||
| 8ed1072c | 2009-08-20 19:17:36 | 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 |