summaryrefslogtreecommitdiff
path: root/doc/examples/reader2.c
diff options
context:
space:
mode:
authorNick Wellnhofer <wellnhofer@aevum.de>2023-04-30 15:28:12 +0200
committerNick Wellnhofer <wellnhofer@aevum.de>2023-04-30 15:48:35 +0200
commitfc119e329069fae2ac7c25bc36ccb8847bac04ad (patch)
tree0e409b312bdf2ae4bcefab865acd5db11d4c514b /doc/examples/reader2.c
parent3da09318114773af4b09aead0f0c917b0ad11928 (diff)
downloadlibxml2-fc119e329069fae2ac7c25bc36ccb8847bac04ad.tar.gz
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.
Diffstat (limited to 'doc/examples/reader2.c')
-rw-r--r--doc/examples/reader2.c8
1 files changed, 0 insertions, 8 deletions
diff --git a/doc/examples/reader2.c b/doc/examples/reader2.c
index 9c2d2e6b..d8d7f924 100644
--- a/doc/examples/reader2.c
+++ b/doc/examples/reader2.c
@@ -103,14 +103,6 @@ int main(int argc, char **argv) {
streamFile(argv[1]);
- /*
- * Cleanup function for the XML library.
- */
- xmlCleanupParser();
- /*
- * this is to debug memory for regression tests
- */
- xmlMemoryDump();
return(0);
}