|
fc119e32
|
2023-04-30T15:28:12
|
|
examples: Don't call xmlCleanupParser and xmlMemoryDump
xmlCleanupParser is dangerous and shouldn't be called in most cases.
Being part of the examples led many people to use it incorrectly.
xmlMemoryDump is an obsolete way to test for memory leaks.
|
|
|
1bd24d44
|
2022-09-02T17:59:09
|
|
Fix compiler warning in examples
|
|
|
c61e1273
|
2022-04-21T06:03:22
|
|
Fix warnings when testing --with-minimum build
There's no simple way to make the doc/examples tests handle different
configurations. But these tests aren't especially valuable, so remove
the result file checks.
|
|
2a350ee9
|
2019-09-30T17:04:54
|
|
Large batch of typo fixes
Closes #109.
|
|
3cf6950b
|
2004-06-16T22:52:59
|
|
fixing a couple of compilation errors when configured with --with-minimum
* doc/examples/io2.c doc/examples/parse4.c: fixing a couple of
compilation errors when configured with --with-minimum
Daniel
|
|
87640d5f
|
2004-04-17T14:58:15
|
|
minor warning cleanup (no change to logic) fixed return value for internal
* xmlschemas.c, xmlwriter.c, doc/examples/parse4.c,
doc/examples/io2.c: minor warning cleanup (no change to logic)
* xinclude: fixed return value for internal function
xmlXIncludeLoadFallback (now always 0 or -1)
|
|
|
88155d85
|
2004-03-25T10:43:16
|
|
Added a couple of parsing examples, Daniel
|