| blob | c5f6c2c943236a590cc9d7fd6427118f01496973 |
4 <html>
5 <head>
6 <!-- Copyright 1999,2000 Clark Cooper <coopercc@netheaven.com>
7 All rights reserved.
8 This is free software. You may distribute or modify according to
9 the terms of the MIT/X License -->
14 </head>
15 <body>
17 <tr>
20 </tr>
21 <tr>
23 <td></td>
24 </tr>
25 </table>
28 <p>Expat is a library, written in C, for parsing XML documents. It's
29 the underlying XML parser for the open source Mozilla project, Perl's
31 other open-source XML parsers.</p>
33 <p>This library is the creation of James Clark, who's also given us
34 groff (an nroff look-alike), Jade (an implemention of ISO's DSSSL
35 stylesheet language for SGML), XP (a Java XML parser package), XT (a
36 Java XSL engine). James was also the technical lead on the XML
37 Working Group at W3C that produced the XML specification.</p>
42 </p>
44 <p>The bulk of this document was originally commissioned as an article
46 Clark Cooper to retain copyright and to distribute it with Expat.
47 This version has been substantially extended to include documentation
48 on features which have been added since the original article was
49 published, and additional information on using the original
50 interface.</p>
52 <hr />
54 <ul>
59 <ul>
61 <ul>
68 </ul>
69 </li>
71 <ul>
78 </ul>
79 </li>
81 <ul>
110 </ul>
111 </li>
113 <ul>
121 </ul>
122 </li>
124 <ul>
144 </ul>
145 </li>
146 </ul>
147 </li>
148 </ul>
150 <hr />
153 <p>Expat is a stream-oriented parser. You register callback (or
154 handler) functions with the parser and then start feeding it the
155 document. As the parser recognizes parts of the document, it will
156 call the appropriate handler for that part (if you've registered one.)
157 The document is fed to the parser in pieces, so you can start parsing
158 before you have all the document. This also allows you to parse really
159 huge documents that won't fit into memory.</p>
161 <p>Expat can be intimidating due to the many kinds of handlers and
162 options you can set. But you only need to learn four functions in
165 <dl>
182 </dl>
186 section also describes in detail the parameters passed to the
187 different types of handlers.</p>
190 above functions (it doesn't need to set a character handler.) The
192 element outline, indenting child elements to distinguish them from the
193 parent element that contains them. The start handler does all the
194 work. It prints two indenting spaces for every level of ancestor
195 elements, then it prints the element and attribute
197 variable.</p>
200 int Depth;
202 void XMLCALL
203 start(void *data, const char *el, const char **attr) {
204 int i;
207 printf(" ");
209 printf("%s", el);
213 }
215 printf("\n");
216 Depth++;
217 } /* End of start handler */
218 </pre>
220 <p>The end tag simply does the bookkeeping work of decrementing
223 void XMLCALL
224 end(void *data, const char *el) {
225 Depth--;
226 } /* End of end handler */
227 </pre>
230 This is used to ensure that the Expat and the callbacks are using the
231 same calling convention in case the compiler options used for Expat
232 itself and the client code are different. Expat tries not to care
233 what the default calling convention is, though it may require that it
234 be compiled with a default convention of "cdecl" on some platforms.
235 For code which uses Expat, however, the calling convention is
237 callbacks should be defined using this annotation.</p>
240 existing working Expat applications don't need to add it (since they
241 are already using the "cdecl" calling convention, or they wouldn't be
242 working). The annotation is only needed if the default calling
243 convention may be something other than "cdecl". To use the annotation
244 safely with older versions of Expat, you can conditionally define it
250 #ifndef XMLCALL
252 #define XMLCALL __cdecl
253 #elif defined(__GNUC__)
254 #define XMLCALL __attribute__((cdecl))
255 #else
256 #define XMLCALL
257 #endif
258 #endif
259 </pre>
261 <p>After creating the parser, the main program just has the job of
262 shoveling the document to the parser so that it can do its work.</p>
264 <hr />
267 <p>The Expat distribution comes as a compressed (with GNU gzip) tar
268 file. You may download the latest version from <a href=
270 unpacking this, cd into the directory. Then follow either the Win32
271 directions or Unix directions below.</p>
275 <p>If you're using the GNU compiler under cygwin, follow the Unix
276 directions in the next section. Otherwise if you have Microsoft's
277 Developer Studio installed, then from Windows Explorer double-click on
278 "expat.dsp" in the lib directory and build and install in the usual
279 manner.</p>
281 <p>Alternatively, you may download the Win32 binary package that
286 <p>First you'll need to run the configure shell script in order to
287 configure the Makefiles and headers for your system.</p>
289 <p>If you're happy with all the defaults that configure picks for you,
290 and you have permission on your system to install into /usr/local, you
291 can install Expat with this sequence of commands:</p>
294 ./configure
295 make
296 make install
297 </pre>
299 <p>There are some options that you can provide to this script, but the
301 can find out all the options available by running configure with just
304 <p>By default, the configure script sets things up so that the library
308 library and header would get installed in
314 <p>Expat's feature set can be configured using a small number of
315 pre-processor definitions. The definition of this symbols does not
316 affect the set of entry points for Expat, only the behavior of the API
317 and the definition of character types in the case of
322 <dd>Include support for using and reporting DTD-based content. If
323 this is defined, default attribute values from an external DTD subset
324 are reported and attribute value normalization occurs based on the
325 type of attributes defined in the external subset. Without
326 this, Expat has a smaller memory footprint and can be faster, but will
327 not load external entities or process conditional sections. This does
328 not affect the set of functions available in the API.</dd>
333 specification is included.</dd>
336 <dd>When defined, character data reported to the application is
337 encoded in UTF-16 using wide characters of the type
344 short</code> is used. Defining this implies
349 integer types to be at least 64 bits in size. This is intended to support
350 processing of very large input streams, where the return values of
354 could overflow. It may not be supported by all compilers, and is turned
355 off by default.</dd>
358 <dd>The number of input bytes of markup context which the parser will
359 ensure are available for reporting via <code><a href=
361 normally set to 1024, and must be set to a positive interger. If this
362 is not defined, the input context will not be available and <code><a
364 always report NULL. Without this, Expat has a smaller memory
365 footprint and can be faster.</dd>
368 <dd>On Windows, this should be set if Expat is going to be linked
369 statically with the code that calls it; this is required to get all
370 the right MSVC magic annotations correct. This is ignored on other
371 platforms.</dd>
372 </dl>
374 <hr />
379 <p>Unless you installed Expat in a location not expected by your
380 compiler and linker, all you have to do to use Expat in your programs
382 in your files that make calls to it and to tell the linker that it
383 needs to link against the Expat library. On Unix systems, this would
385 you'll need to tell the compiler where to look for the Expat header
386 and the linker where to find the Expat library. You may also need to
387 take steps to tell the operating system where to find this library at
388 run time.</p>
390 <p>On a Unix-based system, here's what a Makefile might look like when
391 Expat is installed in a standard location:</p>
394 CC=cc
395 LDFLAGS=
396 LIBS= -lexpat
397 xmlapp: xmlapp.o
398 $(CC) $(LDFLAGS) -o xmlapp xmlapp.o $(LIBS)
399 </pre>
402 the Makefile would look like this:</p>
405 CC=cc
406 CFLAGS= -I/home/me/mystuff/include
407 LDFLAGS=
408 LIBS= -L/home/me/mystuff/lib -lexpat
409 xmlapp: xmlapp.o
410 $(CC) $(LDFLAGS) -o xmlapp xmlapp.o $(LIBS)
411 </pre>
413 <p>You'd also have to set the environment variable
416 LD_LIBRARY_PATH already has some directories in it) in order to run
417 your application.</p>
421 <p>As we saw in the example in the overview, the first step in parsing
422 an XML document with Expat is to create a parser object. There are <a
424 parser object. However, only two of these (<code><a href=
427 constructing a parser for a top-level document. The object returned
428 by these functions is an opaque pointer (i.e. "expat.h" declares it as
429 void *) to data with further internal structure. In order to free the
430 memory associated with this object you must call <code><a href=
433 parser, then your application is responsible for freeing it prior to
436 <p>The objects returned by the parser creation functions are good for
437 parsing only one XML document or external parsed entity. If your
438 application needs to parse many XML documents, then it needs to create
439 a parser object for each one. The best way to deal with this is to
440 create a higher level object that contains all the default
441 initialization you want for your parser objects.</p>
443 <p>Walking through a document hierarchy with a stream oriented parser
444 will require a good stack mechanism in order to keep track of current
445 context. For instance, to answer the simple question, "What element
446 does this text belong to?" requires a stack, since the parser may have
447 descended into other elements that are children of the current one and
448 has encountered this text on the way out.</p>
450 <p>The things you're likely to want to keep on a stack are the
451 currently opened element and it's attributes. You push this
452 information onto the stack in the start handler and you pop it off in
453 the end handler.</p>
455 <p>For some tasks, it is sufficient to just keep information on what
456 the depth of the stack is (or would be if you had one.) The outline
457 program shown above presents one example. Another such task would be
458 skipping over a complete element. When you see the start tag for the
459 element you want to skip, you set a skip flag and record the depth at
460 which the element started. When the end tag handler encounters the
461 same depth, the skipped element has ended and the flag may be
462 cleared. If you follow the convention that the root element starts at
463 1, then you can use the same variable for skip flag and skip
464 depth.</p>
467 void
468 init_info(Parseinfo *info) {
471 /* Other initializations here */
472 } /* End of init_info */
474 void XMLCALL
475 rawstart(void *data, const char *el, const char **attr) {
476 Parseinfo *inf = (Parseinfo *) data;
478 if (! inf->skip) {
479 if (should_skip(inf, el, attr)) {
481 }
482 else
483 start(inf, el, attr); /* This does rest of start handling */
484 }
486 inf->depth++;
487 } /* End of rawstart */
489 void XMLCALL
490 rawend(void *data, const char *el) {
491 Parseinfo *inf = (Parseinfo *) data;
493 inf->depth--;
495 if (! inf->skip)
496 end(inf, el); /* This does rest of end handling */
500 } /* End rawend */
501 </pre>
503 <p>Notice in the above example the difference in how depth is
504 manipulated in the start and end handlers. The end tag handler should
505 be the mirror image of the start tag handler. This is necessary to
506 properly model containment. Since, in the start tag handler, we
509 body. If we'd decided to increment it first thing in the start
510 handler, then we'd have had to decrement it last thing in the end
511 handler.</p>
515 <p>In order to be able to pass information between different handlers
516 without using globals, you'll need to define a data structure to hold
517 the shared variables. You can then tell Expat (with the <code><a href=
519 pointer to this structure to the handlers. This is the first
524 parser itself is passed. When the parser is passed, the user data may
528 <p>One common case where multiple calls to a single handler may need
529 to communicate using an application data structure is the case when
530 content passed to the character data handler (set by <code><a href=
531 "#XML_SetCharacterDataHandler"
533 common first-time mistake with any of the event-oriented interfaces to
534 an XML parser is to expect all the text contained in an element to be
535 reported by a single call to the character data handler. Expat, like
536 many other XML parsers, reports such data as a sequence of calls;
537 there's no way to know when the end of the sequence is reached until a
538 different callback is made. A buffer referenced by the user data
539 structure proves both an effective and convenient place to accumulate
540 character data.</p>
542 <!-- XXX example needed here -->
549 declaration, if present.</p>
551 <p>If an application needs to check the version number (to support
552 alternate processing), it should use the <code><a href=
554 set a handler that uses the information in the XML declaration to
555 determine what to do. This example shows how to check that only a
559 static int wrong_version;
560 static XML_Parser parser;
562 static void XMLCALL
563 xmldecl_handler(void *userData,
564 const XML_Char *version,
565 const XML_Char *encoding,
566 int standalone)
567 {
570 int i;
573 if (version[i] != Version_1_0[i]) {
574 wrong_version = 1;
575 /* also clear all other handlers: */
576 XML_SetCharacterDataHandler(parser, NULL);
577 ...
578 return;
579 }
580 }
581 ...
582 }
583 </pre>
589 performs namespace processing. Under namespace processing, Expat
591 which declare namespaces for the scope of the element in which they
592 occur. This means that your start handler will not see these
593 attributes. Your application can still be informed of these
594 declarations by setting namespace declaration handlers with <a href=
595 "#XML_SetNamespaceDeclHandler"
598 <p>Element type and attribute names that belong to a given namespace
599 are passed to the appropriate handler in expanded form. By default
600 this expanded form is a concatenation of the namespace URI, the
603 name (i.e. the part after the colon). Names with undeclared prefixes
604 are not well-formed when namespace processing is enabled, and will
605 trigger an error. Unprefixed attribute names are never expanded,
606 and unprefixed element names are only expanded when they are in the
607 scope of a default namespace.</p>
612 an explicit prefix is a concatenation of: URI, separator, local name,
613 separator, prefix.</p>
615 <p>You can set handlers for the start of a namespace declaration and
616 for the end of a scope of a declaration with the <code><a href=
618 function. The StartNamespaceDeclHandler is called prior to the start
619 tag handler and the EndNamespaceDeclHandler is called after the
620 corresponding end tag that ends the namespace's scope. The namespace
621 start handler gets passed the prefix and URI for the namespace. For a
622 default namespace declaration (xmlns='...'), the prefix will be null.
623 The URI will be null for the case where the default namespace is being
624 unset. The namespace end handler just gets the prefix for the closing
625 scope.</p>
627 <p>These handlers are called for each declaration. So if, for
628 instance, a start tag had three namespace declarations, then the
629 StartNamespaceDeclHandler would be called three times before the start
630 tag handler is called, once for each declaration.</p>
634 <p>While XML is based on Unicode, and every XML processor is required
636 other encodings may be declared in XML documents or entities. For the
637 main document, an XML declaration may contain an encoding
638 declaration:</p>
639 <pre>
641 </pre>
643 <p>External parsed entities may begin with a text declaration, which
644 looks like an XML declaration with just an encoding declaration:</p>
645 <pre>
647 </pre>
649 <p>With Expat, you may also specify an encoding at the time of
650 creating a parser. This is useful when the encoding information may
651 come from a source outside the document itself (like a higher level
652 protocol.)</p>
655 in Expat:</p>
656 <ul>
661 </ul>
663 <p>Anything else discovered in an encoding declaration or in the
664 protocol encoding specified in the parser constructor, triggers a call
667 structure. Your handler must fill in this structure and return
669 encoding. Otherwise the handler should return
671 to an optional application data structure that you may indicate when
672 you set the handler.</p>
674 <p>Expat places restrictions on character encodings that it can
676 include file:</p>
677 <ol>
678 <li>Every ASCII character that can appear in a well-formed XML document
679 must be represented by a single byte, and that byte must correspond to
680 it's ASCII encoding (except for the characters $@\^'{}~)</li>
682 <li>All characters encoded must have Unicode scalar values less than or
685 <li>No character may be encoded by more that one distinct sequence of
686 bytes</li>
687 </ol>
690 correspond to the 1st byte of an encoding sequence. If the value in
691 the array for a byte is zero or positive, then the byte is a single
692 byte encoding that encodes the Unicode scalar value contained in the
693 array. A -1 in this array indicates a malformed byte. If the value is
695 sequence respectively. Multi-byte sequences are sent to the convert
697 function should return the Unicode scalar value for the sequence or -1
698 if the sequence is malformed.</p>
700 <p>One pitfall that novice Expat users are likely to fall into is that
701 although Expat may accept input in various encodings, the strings that
703 (depending on how Expat was compiled). Your application is responsible
704 for any translation of these strings into other encodings.</p>
708 <p>Expat does not read or parse external entities directly. Note that
709 any external DTD is a special case of an external entity. If you've
711 references are silently ignored. Otherwise, it calls your handler with
712 the information needed to read and parse the external entity.</p>
714 <p>Your handler isn't actually responsible for parsing the entity, but
715 it is responsible for creating a subsidiary parser with <code><a href=
716 "#XML_ExternalEntityParserCreate"
719 other data structures initialized from the parent parser. You may then
722 parser. Since external entities my refer to other external entities,
723 your handler should be prepared to be called recursively.</p>
727 <p>In order to parse parameter entities, before starting the parse,
730 arguments:</p>
731 <dl>
735 <dd>Parse parameter entites and the external subset unless
739 </dl>
741 <p>In order to read an external DTD, you also have to set an external
742 entity reference handler as described above.</p>
747 parsing temporarily from within a handler function, even if more data
748 has already been passed into the parser. Applications for this
749 include</p>
751 <ul>
755 <li>Delaying further processing until additional information is
756 available from some other source.</li>
758 <li>Adjusting processor load as task priorities shift within an
759 application.</li>
761 <li>Stopping parsing completely (simply free or reset the parser
762 instead of resuming in the outer parsing loop). This can be useful
763 if a application-domain error is found in the XML being parsed or if
764 the result of the parse is determined not to be useful after
765 all.</li>
766 </ul>
768 <p>To take advantage of this feature, the main parsing loop of an
769 application needs to support this specifically. It cannot be
770 supported with a parsing loop compatible with Expat 1.95.7 or
771 earlier (though existing loops will continue to work without
772 supporting the stop/resume feature).</p>
774 <p>An application that uses this feature for a single parser will have
775 the rough structure (in pseudo-code):</p>
778 fd = open_input()
779 p = create_parser()
781 if parse_xml(p, fd) {
782 /* suspended */
784 int suspended = 1;
786 while (suspended) {
787 do_something_else()
788 if ready_to_resume() {
789 suspended = continue_parsing(p, fd);
790 }
791 }
792 }
793 </pre>
795 <p>An application that may resume any of several parsers based on
796 input (either from the XML being parsed or some other source) will
797 certainly have more interesting control structures.</p>
800 function mentioned in the pseudo-code above:</p>
803 #define BUFF_SIZE 10240
805 /* Parse a document from the open file descriptor 'fd' until the parse
806 is complete (the document has been completely parsed, or there's
807 been an error), or the parse is stopped. Return non-zero when
808 the parse is merely suspended.
809 */
810 int
811 parse_xml(XML_Parser p, int fd)
812 {
813 for (;;) {
814 int last_chunk;
815 int bytes_read;
816 enum XML_Status status;
818 void *buff = XML_GetBuffer(p, BUFF_SIZE);
819 if (buff == NULL) {
820 /* handle error... */
821 return 0;
822 }
823 bytes_read = read(fd, buff, BUFF_SIZE);
825 /* handle error... */
826 return 0;
827 }
828 status = XML_ParseBuffer(p, bytes_read, bytes_read == 0);
829 switch (status) {
830 case XML_STATUS_ERROR:
831 /* handle error... */
832 return 0;
833 case XML_STATUS_SUSPENDED:
834 return 1;
835 }
836 if (bytes_read == 0)
837 return 0;
838 }
839 }
840 </pre>
843 somewhat simpler, since it only need deal with the return code from
846 function:</p>
849 /* Continue parsing a document which had been suspended. The 'p' and
850 'fd' arguments are the same as passed to parse_xml(). Return
851 non-zero when the parse is suspended.
852 */
853 int
854 continue_parsing(XML_Parser p, int fd)
855 {
856 enum XML_Status status = XML_ResumeParser(p);
857 switch (status) {
858 case XML_STATUS_ERROR:
859 /* handle error... */
860 return 0;
861 case XML_ERROR_NOT_SUSPENDED:
862 /* handle error... */
863 return 0;.
864 case XML_STATUS_SUSPENDED:
865 return 1;
866 }
867 return parse_xml(p, fd);
868 }
869 </pre>
871 <p>Now that we've seen what a mess the top-level parsing loop can
872 become, what have we gained? Very simply, we can now use the <code><a
874 parsing, without having to go to great lengths to avoid additional
875 processing that we're expecting to ignore. As a bonus, we get to stop
877 ready.</p>
881 takes two arguments; the parser being stopped and a flag indicating
882 whether the parse can be resumed in the future.</p>
884 <!-- XXX really need more here -->
887 <hr />
888 <!-- ================================================================ -->
895 XML_Parser XMLCALL
896 XML_ParserCreate(const XML_Char *encoding);
897 </pre>
899 Construct a new parser. If encoding is non-null, it specifies a
900 character encoding to use for the document. This overrides the document
901 encoding declaration. There are four built-in encodings:
902 <ul>
907 </ul>
908 Any other value will invoke a call to the UnknownEncodingHandler.
909 </div>
912 XML_Parser XMLCALL
913 XML_ParserCreateNS(const XML_Char *encoding,
914 XML_Char sep);
915 </pre>
917 Constructs a new parser that has namespace processing in effect. Namespace
918 expanded element names and attribute names are returned as a concatenation
921 of an URI. Since Expat does not check namespace URIs for conformance, the
922 only safe choice for a namespace separator is a character that is illegal
926 the local part will be concatenated without any separator - this is intended
927 to support RDF processors. It is a programming error to use the null separator
931 XML_Parser XMLCALL
932 XML_ParserCreate_MM(const XML_Char *encoding,
933 const XML_Memory_Handling_Suite *ms,
934 const XML_Char *sep);
935 </pre>
937 typedef struct {
938 void *(XMLCALL *malloc_fcn)(size_t size);
939 void *(XMLCALL *realloc_fcn)(void *ptr, size_t size);
940 void (XMLCALL *free_fcn)(void *ptr);
941 } XML_Memory_Handling_Suite;
942 </pre>
944 <p>Construct a new parser using the suite of memory handling functions
947 non NULL, then namespace processing is enabled in the created parser
948 and the character pointed at by sep is used as the separator between
949 the namespace URI and the local part of the name.</p>
950 </div>
953 XML_Parser XMLCALL
954 XML_ExternalEntityParserCreate(XML_Parser p,
955 const XML_Char *context,
956 const XML_Char *encoding);
957 </pre>
960 general entity. Context is the context argument passed in a call to a
961 ExternalEntityRefHandler. Other state information such as handlers,
962 user data, namespace processing is inherited from the parser passed as
963 the 1st argument. So you shouldn't need to call any of the behavior
964 changing functions on this parser (unless you want it to act
965 differently than the parent parser).
966 </div>
969 void XMLCALL
970 XML_ParserFree(XML_Parser p);
971 </pre>
973 Free memory used by the parser. Your application is responsible for
975 </div>
978 XML_Bool XMLCALL
979 XML_ParserReset(XML_Parser p,
980 const XML_Char *encoding);
981 </pre>
983 Clean up the memory structures maintained by the parser so that it may
985 ready to start parsing a new document. All handlers are cleared from
986 the parser, except for the unknownEncodingHandler. The parser's external
987 state is re-initialized except for the values of ns and ns_triplets.
988 This function may not be used on a parser created using <code><a href=
993 </div>
1000 XML_GetBuffer</a></code> must not be called from within a handler
1001 unless they operate on a separate parser instance, that is, one that
1002 did not call the handler. For example, it is OK to call the parsing
1004 if they apply to the parser created by
1009 should be considerably less than the maximum value for an integer,
1010 as it could create an integer overflow situation if the added
1011 lengths of a buffer and the unprocessed portion of the previous buffer
1012 exceed the maximum integer value. Input data at the end of a buffer
1013 will remain unprocessed if it is part of an XML token for which the
1014 end is not part of that buffer.</p>
1017 enum XML_Status XMLCALL
1018 XML_Parse(XML_Parser p,
1019 const char *s,
1020 int len,
1021 int isFinal);
1022 </pre>
1024 enum XML_Status {
1025 XML_STATUS_ERROR = 0,
1026 XML_STATUS_OK = 1
1027 };
1028 </pre>
1031 containing part (or perhaps all) of the document. The number of bytes of s
1037 piece of the document. Frequently, the last piece is empty (i.e.
1041 </div>
1044 enum XML_Status XMLCALL
1045 XML_ParseBuffer(XML_Parser p,
1046 int len,
1047 int isFinal);
1048 </pre>
1051 except in this case Expat provides the buffer. By obtaining the
1054 copying of the input.
1055 </div>
1058 void * XMLCALL
1059 XML_GetBuffer(XML_Parser p,
1060 int len);
1061 </pre>
1064 into. A NULL value is returned if Expat can't allocate enough memory for
1065 this buffer. This has to be called prior to every call to
1067 typical use would look like this:
1070 for (;;) {
1071 int bytes_read;
1072 void *buff = XML_GetBuffer(p, BUFF_SIZE);
1073 if (buff == NULL) {
1074 /* handle error */
1075 }
1077 bytes_read = read(docfd, buff, BUFF_SIZE);
1079 /* handle error */
1080 }
1082 if (! XML_ParseBuffer(p, bytes_read, bytes_read == 0)) {
1083 /* handle parse error */
1084 }
1086 if (bytes_read == 0)
1087 break;
1088 }
1089 </pre>
1090 </div>
1093 enum XML_Status XMLCALL
1094 XML_StopParser(XML_Parser p,
1095 XML_Bool resumable);
1096 </pre>
1104 call-backs may still follow because they would otherwise get
1105 lost, including
1106 <ul>
1107 <li> the end element handler for empty elements when stopped in the
1108 start element handler,</li>
1109 <li> the end namespace declaration handler when stopped in the end
1110 element handler,</li>
1111 <li> the character data handler when stopped in the character data handler
1112 while making multiple call-backs on a contiguous chunk of characters,</li>
1113 </ul>
1114 and possibly others.</p>
1116 <p>This can be called from most handlers, including DTD related
1117 call-backs, except when parsing an external parameter entity and
1121 are:</p>
1122 <dl>
1129 </dl>
1131 <p>Since the stop/resume feature requires application support in the
1132 outer parsing loop, it is an error to call this function for a parser
1147 This will be applied to the current parser instance only, that is, if
1148 there is a parent parser then it will continue parsing when the
1149 external entity reference handler returns. It is up to the
1150 implementation of that handler to call <code><a href=
1152 (recursively), if one wants to stop parsing altogether.</p>
1158 </div>
1161 enum XML_Status XMLCALL
1162 XML_ResumeParser(XML_Parser p);
1163 </pre>
1167 within a handler call-back. Returns same status codes as <code><a
1171 parser was not currently suspended.</p>
1174 This must be called on the most deeply nested child parser instance
1175 first, and on its parent parser only after the child parser has
1176 finished, to be applied recursively until the document entity's parser
1177 is restarted. That is, the parent parser will not resume by itself
1178 and it is up to the application to call <code><a href=
1180 appropriate moment.</p>
1183 </div>
1186 void XMLCALL
1187 XML_GetParsingStatus(XML_Parser p,
1188 XML_ParsingStatus *status);
1189 </pre>
1191 enum XML_Parsing {
1192 XML_INITIALIZED,
1193 XML_PARSING,
1194 XML_FINISHED,
1195 XML_SUSPENDED
1196 };
1198 typedef struct {
1199 enum XML_Parsing parsing;
1200 XML_Bool finalBuffer;
1201 } XML_ParsingStatus;
1202 </pre>
1204 <p>Returns status of parser with respect to being initialized,
1205 parsing, finished, or suspended, and whether the final buffer is being
1207 NULL.</p>
1210 </div>
1215 <p>Although handlers are typically set prior to parsing and left alone, an
1216 application may choose to set or change the handler for a parsing event
1217 while the parse is in progress. For instance, your application may choose
1219 way it could do this is to set the character handler when a para start tag
1220 is seen, and unset it for the corresponding end tag.</p>
1223 appropriate handler setter. None of the handler setting functions have
1224 a return value.</p>
1226 <p>Your handlers will be receiving strings in arrays of type
1230 Note that you'll receive them in this form independent of the original
1231 encoding of the document.</p>
1235 void XMLCALL
1236 XML_SetStartElementHandler(XML_Parser p,
1237 XML_StartElementHandler start);
1238 </pre>
1240 typedef void
1241 (XMLCALL *XML_StartElementHandler)(void *userData,
1242 const XML_Char *name,
1243 const XML_Char **atts);
1244 </pre>
1245 <p>Set handler for start (and empty) tags. Attributes are passed to the start
1246 handler as a pointer to a vector of char pointers. Each attribute seen in
1247 a start (or empty) tag occupies 2 consecutive places in this vector: the
1248 attribute name followed by the attribute value. These pairs are terminated
1249 by a null pointer.</p>
1250 <p>Note that an empty tag generates a call to both start and end handlers
1251 (in that order).</p>
1252 </div>
1256 void XMLCALL
1257 XML_SetEndElementHandler(XML_Parser p,
1258 XML_EndElementHandler);
1259 </pre>
1261 typedef void
1262 (XMLCALL *XML_EndElementHandler)(void *userData,
1263 const XML_Char *name);
1264 </pre>
1265 <p>Set handler for end (and empty) tags. As noted above, an empty tag
1266 generates a call to both start and end handlers.</p>
1267 </div>
1271 void XMLCALL
1272 XML_SetElementHandler(XML_Parser p,
1273 XML_StartElementHandler start,
1274 XML_EndElementHandler end);
1275 </pre>
1277 </div>
1281 void XMLCALL
1282 XML_SetCharacterDataHandler(XML_Parser p,
1283 XML_CharacterDataHandler charhndl)
1284 </pre>
1286 typedef void
1287 (XMLCALL *XML_CharacterDataHandler)(void *userData,
1288 const XML_Char *s,
1289 int len);
1290 </pre>
1291 <p>Set a text handler. The string your handler receives
1293 to deal with the end of the string. A single block of contiguous text
1294 free of markup may still result in a sequence of calls to this handler.
1295 In other words, if you're searching for a pattern in the text, it may
1296 be split across calls to this handler. Note: Setting this handler to NULL
1298 processing such a single block of contiguous markup-free text, as the parser
1299 will continue calling back until the end of the block is reached.</p>
1300 </div>
1304 void XMLCALL
1305 XML_SetProcessingInstructionHandler(XML_Parser p,
1306 XML_ProcessingInstructionHandler proc)
1307 </pre>
1309 typedef void
1310 (XMLCALL *XML_ProcessingInstructionHandler)(void *userData,
1311 const XML_Char *target,
1312 const XML_Char *data);
1314 </pre>
1315 <p>Set a handler for processing instructions. The target is the first word
1316 in the processing instruction. The data is the rest of the characters in
1317 it after skipping all whitespace after the initial word.</p>
1318 </div>
1322 void XMLCALL
1323 XML_SetCommentHandler(XML_Parser p,
1324 XML_CommentHandler cmnt)
1325 </pre>
1327 typedef void
1328 (XMLCALL *XML_CommentHandler)(void *userData,
1329 const XML_Char *data);
1330 </pre>
1331 <p>Set a handler for comments. The data is all text inside the comment
1332 delimiters.</p>
1333 </div>
1337 void XMLCALL
1338 XML_SetStartCdataSectionHandler(XML_Parser p,
1339 XML_StartCdataSectionHandler start);
1340 </pre>
1342 typedef void
1343 (XMLCALL *XML_StartCdataSectionHandler)(void *userData);
1344 </pre>
1346 </div>
1350 void XMLCALL
1351 XML_SetEndCdataSectionHandler(XML_Parser p,
1352 XML_EndCdataSectionHandler end);
1353 </pre>
1355 typedef void
1356 (XMLCALL *XML_EndCdataSectionHandler)(void *userData);
1357 </pre>
1359 </div>
1363 void XMLCALL
1364 XML_SetCdataSectionHandler(XML_Parser p,
1365 XML_StartCdataSectionHandler start,
1366 XML_EndCdataSectionHandler end)
1367 </pre>
1369 </div>
1373 void XMLCALL
1374 XML_SetDefaultHandler(XML_Parser p,
1375 XML_DefaultHandler hndl)
1376 </pre>
1378 typedef void
1379 (XMLCALL *XML_DefaultHandler)(void *userData,
1380 const XML_Char *s,
1381 int len);
1382 </pre>
1384 <p>Sets a handler for any characters in the document which wouldn't
1385 otherwise be handled. This includes both data for which no handlers
1386 can be set (like some kinds of DTD declarations) and data which could
1387 be reported but which currently has no handler set. The characters
1388 are passed exactly as they were present in the XML document except
1390 normalized. Note that a byte order mark character is not passed to the
1391 default handler. There are no guarantees about how characters are
1392 divided between calls to the default handler: for example, a comment
1393 might be split between multiple calls. Setting the handler with
1394 this call has the side effect of turning off expansion of references
1395 to internally defined general entities. Instead these references are
1396 passed to the default handler.</p>
1400 </div>
1404 void XMLCALL
1405 XML_SetDefaultHandlerExpand(XML_Parser p,
1406 XML_DefaultHandler hndl)
1407 </pre>
1409 typedef void
1410 (XMLCALL *XML_DefaultHandler)(void *userData,
1411 const XML_Char *s,
1412 int len);
1413 </pre>
1414 <p>This sets a default handler, but doesn't inhibit the expansion of
1415 internal entity references. The entity reference will not be passed
1416 to the default handler.</p>
1420 </div>
1424 void XMLCALL
1425 XML_SetExternalEntityRefHandler(XML_Parser p,
1426 XML_ExternalEntityRefHandler hndl)
1427 </pre>
1429 typedef int
1430 (XMLCALL *XML_ExternalEntityRefHandler)(XML_Parser p,
1431 const XML_Char *context,
1432 const XML_Char *base,
1433 const XML_Char *systemId,
1434 const XML_Char *publicId);
1435 </pre>
1436 <p>Set an external entity reference handler. This handler is also
1437 called for processing an external DTD subset if parameter entity parsing
1445 valid only until the handler returns, so if the referenced entity is
1447 only when the entity is a parameter entity, which is how one can
1448 differentiate between general and parameter entities.</p>
1451 system identifiers. It is set by <code><a
1455 identifier specified in the entity declaration and is never NULL.</p>
1457 <p>There are a couple of ways in which this handler differs from
1458 others. First, this handler returns a status indicator (an
1460 handling of the external entity reference. Returning
1462 calling parser to return an
1465 <p>Second, instead of having the user data as its first argument, it
1466 receives the parser that encountered the entity reference. This, along
1467 with the context parameter, may be used as arguments to a call to
1470 parser, the body of the external entity can be recursively parsed.</p>
1472 <p>Since this handler may be called recursively, it should not be saving
1473 information into global or static variables.</p>
1474 </div>
1477 void XMLCALL
1478 XML_SetExternalEntityRefHandlerArg(XML_Parser p,
1479 void *arg)
1480 </pre>
1482 <p>Set the argument passed to the ExternalEntityRefHandler. If
1486 NULL, the argument passed to the handler function will be the parser
1487 object itself.</p>
1491 ExternalEntityRefHandler do not match. This function takes a
1494 but will not be corrected before Expat 2.0 (at the earliest) to avoid
1495 causing compiler warnings for code that's known to work with this
1496 API. It is the responsibility of the application code to know the
1497 actual type of the argument passed to the handler and to manage it
1498 properly.</p>
1499 </div>
1503 void XMLCALL
1504 XML_SetSkippedEntityHandler(XML_Parser p,
1505 XML_SkippedEntityHandler handler)
1506 </pre>
1508 typedef void
1509 (XMLCALL *XML_SkippedEntityHandler)(void *userData,
1510 const XML_Char *entityName,
1511 int is_parameter_entity);
1512 </pre>
1514 <ol>
1515 <li>An entity reference is encountered for which no declaration
1517 <li>An internal entity reference is read, but not expanded, because
1519 has been called.</li>
1520 </ol>
1522 a parameter entity and zero for a general entity.</p> <p>Note: skipped
1523 parameter entities in declarations and skipped general entities in
1524 attribute values cannot be reported, because the event would be out of
1525 sync with the reporting of the declarations or attribute values</p>
1526 </div>
1530 void XMLCALL
1531 XML_SetUnknownEncodingHandler(XML_Parser p,
1532 XML_UnknownEncodingHandler enchandler,
1533 void *encodingHandlerData)
1534 </pre>
1536 typedef int
1537 (XMLCALL *XML_UnknownEncodingHandler)(void *encodingHandlerData,
1538 const XML_Char *name,
1539 XML_Encoding *info);
1541 typedef struct {
1542 int map[256];
1543 void *data;
1544 int (XMLCALL *convert)(void *data, const char *s);
1545 void (XMLCALL *release)(void *data);
1546 } XML_Encoding;
1547 </pre>
1552 given parser.</p> <p>If the handler knows how to deal with an encoding
1556 at most once per parsed (external) entity. The optional application
1558 the handler.</p>
1560 <p>The map array contains information for every possible possible leading
1562 a single byte sequence and the byte encodes that Unicode value. If the
1563 value is -1, then that byte is invalid as the initial byte in a sequence.
1565 bytes in the sequence and the actual conversion is accomplished by a
1566 call to the function pointed at by convert. This function may return -1
1567 if the sequence itself is invalid. The convert pointer may be null if
1568 there are only single byte codes. The data parameter passed to the convert
1571 bytes to be converted.</p>
1574 parser when it is finished with the encoding. It may be NULL.</p>
1575 </div>
1579 void XMLCALL
1580 XML_SetStartNamespaceDeclHandler(XML_Parser p,
1581 XML_StartNamespaceDeclHandler start);
1582 </pre>
1584 typedef void
1585 (XMLCALL *XML_StartNamespaceDeclHandler)(void *userData,
1586 const XML_Char *prefix,
1587 const XML_Char *uri);
1588 </pre>
1589 <p>Set a handler to be called when a namespace is declared. Namespace
1590 declarations occur inside start tags. But the namespace declaration start
1591 handler is called before the start tag handler for each namespace declared
1592 in that start tag.</p>
1593 </div>
1597 void XMLCALL
1598 XML_SetEndNamespaceDeclHandler(XML_Parser p,
1599 XML_EndNamespaceDeclHandler end);
1600 </pre>
1602 typedef void
1603 (XMLCALL *XML_EndNamespaceDeclHandler)(void *userData,
1604 const XML_Char *prefix);
1605 </pre>
1606 <p>Set a handler to be called when leaving the scope of a namespace
1607 declaration. This will be called, for each namespace declaration,
1608 after the handler for the end tag of the element in which the
1609 namespace was declared.</p>
1610 </div>
1614 void XMLCALL
1615 XML_SetNamespaceDeclHandler(XML_Parser p,
1616 XML_StartNamespaceDeclHandler start,
1617 XML_EndNamespaceDeclHandler end)
1618 </pre>
1620 </div>
1624 void XMLCALL
1625 XML_SetXmlDeclHandler(XML_Parser p,
1626 XML_XmlDeclHandler xmldecl);
1627 </pre>
1629 typedef void
1630 (XMLCALL *XML_XmlDeclHandler)(void *userData,
1631 const XML_Char *version,
1632 const XML_Char *encoding,
1633 int standalone);
1634 </pre>
1635 <p>Sets a handler that is called for XML declarations and also for
1636 text declarations discovered in external entities. The way to
1641 standalone parameter in the declaration, that it was given as no, or
1642 that it was given as yes.</p>
1643 </div>
1647 void XMLCALL
1648 XML_SetStartDoctypeDeclHandler(XML_Parser p,
1649 XML_StartDoctypeDeclHandler start);
1650 </pre>
1652 typedef void
1653 (XMLCALL *XML_StartDoctypeDeclHandler)(void *userData,
1654 const XML_Char *doctypeName,
1655 const XML_Char *sysid,
1656 const XML_Char *pubid,
1657 int has_internal_subset);
1658 </pre>
1659 <p>Set a handler that is called at the start of a DOCTYPE declaration,
1662 will be non-zero if the DOCTYPE declaration has an internal subset.</p>
1663 </div>
1667 void XMLCALL
1668 XML_SetEndDoctypeDeclHandler(XML_Parser p,
1669 XML_EndDoctypeDeclHandler end);
1670 </pre>
1672 typedef void
1673 (XMLCALL *XML_EndDoctypeDeclHandler)(void *userData);
1674 </pre>
1675 <p>Set a handler that is called at the end of a DOCTYPE declaration,
1676 after parsing any external subset.</p>
1677 </div>
1681 void XMLCALL
1682 XML_SetDoctypeDeclHandler(XML_Parser p,
1683 XML_StartDoctypeDeclHandler start,
1684 XML_EndDoctypeDeclHandler end);
1685 </pre>
1687 </div>
1691 void XMLCALL
1692 XML_SetElementDeclHandler(XML_Parser p,
1693 XML_ElementDeclHandler eldecl);
1694 </pre>
1696 typedef void
1697 (XMLCALL *XML_ElementDeclHandler)(void *userData,
1698 const XML_Char *name,
1699 XML_Content *model);
1700 </pre>
1702 enum XML_Content_Type {
1703 XML_CTYPE_EMPTY = 1,
1704 XML_CTYPE_ANY,
1705 XML_CTYPE_MIXED,
1706 XML_CTYPE_NAME,
1707 XML_CTYPE_CHOICE,
1708 XML_CTYPE_SEQ
1709 };
1711 enum XML_Content_Quant {
1712 XML_CQUANT_NONE,
1713 XML_CQUANT_OPT,
1714 XML_CQUANT_REP,
1715 XML_CQUANT_PLUS
1716 };
1718 typedef struct XML_cp XML_Content;
1720 struct XML_cp {
1721 enum XML_Content_Type type;
1722 enum XML_Content_Quant quant;
1723 const XML_Char * name;
1724 unsigned int numchildren;
1725 XML_Content * children;
1726 };
1727 </pre>
1728 <p>Sets a handler for element declarations in a DTD. The handler gets
1729 called with the name of the element in the declaration and a pointer
1730 to a structure that contains the element model. It is the
1731 application's responsibility to free this data structure using
1745 XML_CTYPE_NAME with no quantification. Only the root node can be type
1753 name.</p>
1756 indicate a choice or sequence respectively. The
1759 </div>
1763 void XMLCALL
1764 XML_SetAttlistDeclHandler(XML_Parser p,
1765 XML_AttlistDeclHandler attdecl);
1766 </pre>
1768 typedef void
1769 (XMLCALL *XML_AttlistDeclHandler)(void *userData,
1770 const XML_Char *elname,
1771 const XML_Char *attname,
1772 const XML_Char *att_type,
1773 const XML_Char *dflt,
1774 int isrequired);
1775 </pre>
1776 <p>Set a handler for attlist declarations in the DTD. This handler is
1778 with multiple attributes declared will generate multiple calls to this
1780 element for which the attribute is being declared. The attribute name
1783 type in the declaration with whitespace removed.</p>
1788 parameter, which will be true in the case of "#REQUIRED" attributes.
1789 Attributes which are "#FIXED" will have also have a true
1792 </div>
1796 void XMLCALL
1797 XML_SetEntityDeclHandler(XML_Parser p,
1798 XML_EntityDeclHandler handler);
1799 </pre>
1801 typedef void
1802 (XMLCALL *XML_EntityDeclHandler)(void *userData,
1803 const XML_Char *entityName,
1804 int is_parameter_entity,
1805 const XML_Char *value,
1806 int value_length,
1807 const XML_Char *base,
1808 const XML_Char *systemId,
1809 const XML_Char *publicId,
1810 const XML_Char *notationName);
1811 </pre>
1812 <p>Sets a handler that will be called for all entity declarations.
1814 case of parameter entities and zero otherwise.</p>
1822 legal to have zero-length values. Instead check for whether or not
1824 argument will have a non-NULL value only for unparsed entity
1825 declarations.</p>
1826 </div>
1830 void XMLCALL
1831 XML_SetUnparsedEntityDeclHandler(XML_Parser p,
1832 XML_UnparsedEntityDeclHandler h)
1833 </pre>
1835 typedef void
1836 (XMLCALL *XML_UnparsedEntityDeclHandler)(void *userData,
1837 const XML_Char *entityName,
1838 const XML_Char *base,
1839 const XML_Char *systemId,
1840 const XML_Char *publicId,
1841 const XML_Char *notationName);
1842 </pre>
1843 <p>Set a handler that receives declarations of unparsed entities. These
1844 are entity declarations that have a notation (NDATA) field:</p>
1848 </pre></div>
1849 <p>This handler is obsolete and is provided for backwards
1852 </div>
1856 void XMLCALL
1857 XML_SetNotationDeclHandler(XML_Parser p,
1858 XML_NotationDeclHandler h)
1859 </pre>
1861 typedef void
1862 (XMLCALL *XML_NotationDeclHandler)(void *userData,
1863 const XML_Char *notationName,
1864 const XML_Char *base,
1865 const XML_Char *systemId,
1866 const XML_Char *publicId);
1867 </pre>
1869 </div>
1873 void XMLCALL
1874 XML_SetNotStandaloneHandler(XML_Parser p,
1875 XML_NotStandaloneHandler h)
1876 </pre>
1878 typedef int
1879 (XMLCALL *XML_NotStandaloneHandler)(void *userData);
1880 </pre>
1882 This happens when there is an external subset or a reference to a
1883 parameter entity, but does not have standalone set to "yes" in an XML
1886 error.</p>
1887 </div>
1891 <p>These are the functions you'll want to call when the parse
1893 occurred), although the position reporting functions are useful outside
1894 of errors. The position reported is the byte position (in the original
1895 document or entity encoding) of the first of the sequence of
1896 characters that generated the current event (or the error that caused
1898 exceptions are callbacks trigged by declarations in the document
1899 prologue, in which case they exact position reported is somewhere in the
1900 relevant markup, but not necessarily as meaningful as for other
1901 events.</p>
1903 <p>The position reporting functions are accurate only outside of the
1904 DTD. In other words, they usually return bogus information when
1905 called from within a DTD declaration handler.</p>
1908 enum XML_Error XMLCALL
1909 XML_GetErrorCode(XML_Parser p);
1910 </pre>
1912 Return what type of error has occurred.
1913 </div>
1916 const XML_LChar * XMLCALL
1917 XML_ErrorString(enum XML_Error code);
1918 </pre>
1920 Return a string describing the error corresponding to code.
1921 The code should be one of the enums that can be returned from
1923 </div>
1926 XML_Index XMLCALL
1927 XML_GetCurrentByteIndex(XML_Parser p);
1928 </pre>
1930 Return the byte offset of the position. This always corresponds to
1934 </div>
1937 XML_Size XMLCALL
1938 XML_GetCurrentLineNumber(XML_Parser p);
1939 </pre>
1941 Return the line number of the position. The first line is reported as
1943 </div>
1946 XML_Size XMLCALL
1947 XML_GetCurrentColumnNumber(XML_Parser p);
1948 </pre>
1950 Return the offset, from the beginning of the current line, of
1951 the position.
1952 </div>
1955 int XMLCALL
1956 XML_GetCurrentByteCount(XML_Parser p);
1957 </pre>
1959 Return the number of bytes in the current event. Returns
1961 entity and for the end-tag event for empty element tags (the later can
1962 be used to distinguish empty-element tags from empty elements using
1963 separate start and end tags).
1964 </div>
1967 const char * XMLCALL
1968 XML_GetInputContext(XML_Parser p,
1969 int *offset,
1970 int *size);
1971 </pre>
1974 <p>Returns the parser's input buffer, sets the integer pointed at by
1977 the size of the returned buffer.</p>
1979 <p>This should only be called from within a handler during an active
1980 parse and the returned buffer should only be referred to from within
1981 the handler that made the call. This input buffer contains the
1982 untranslated bytes of the input.</p>
1984 <p>Only a limited amount of context is kept, so if the event
1985 triggering a call spans over a very large amount of input, the actual
1986 parse position may be before the beginning of the buffer.</p>
1989 return NULL.</p>
1990 </div>
1994 <p>The functions in this section either obtain state information from
1995 the parser or can be used to dynamicly set parser options.</p>
1998 void XMLCALL
1999 XML_SetUserData(XML_Parser p,
2000 void *userData);
2001 </pre>
2003 This sets the user data pointer that gets passed to handlers. It
2004 overwrites any previous value for this pointer. Note that the
2005 application is responsible for freeing the memory associated with
2007 call this when there's already a pointer there, and you haven't freed
2008 the memory associated with it, then you've probably just leaked
2009 memory.
2010 </div>
2013 void * XMLCALL
2014 XML_GetUserData(XML_Parser p);
2015 </pre>
2017 This returns the user data pointer that gets passed to handlers.
2018 It is actually implemented as a macro.
2019 </div>
2022 void XMLCALL
2023 XML_UseParserAsHandlerArg(XML_Parser p);
2024 </pre>
2026 After this is called, handlers receive the parser in their
2030 </div>
2033 enum XML_Status XMLCALL
2034 XML_SetBase(XML_Parser p,
2035 const XML_Char *base);
2036 </pre>
2038 Set the base to be used for resolving relative URIs in system
2040 there's no memory to store base, otherwise it's
2042 </div>
2045 const XML_Char * XMLCALL
2046 XML_GetBase(XML_Parser p);
2047 </pre>
2049 Return the base for resolving relative URIs.
2050 </div>
2053 int XMLCALL
2054 XML_GetSpecifiedAttributeCount(XML_Parser p);
2055 </pre>
2057 When attributes are reported to the start handler in the atts vector,
2058 attributes that were explicitly set in the element occur before any
2059 attributes that receive their value from default information in an
2060 ATTLIST declaration. This function returns the number of attributes
2061 that were explicitly set times two, thus giving the offset in the
2063 attribute set due to defaults. It supplies information for the last
2064 call to a start handler. If called inside a start handler, then that
2065 means the current call.
2066 </div>
2069 int XMLCALL
2070 XML_GetIdAttributeIndex(XML_Parser p);
2071 </pre>
2073 Returns the index of the ID attribute passed in the atts array in the
2076 attribute. If called inside a start handler, then that means the
2077 current call.
2078 </div>
2081 enum XML_Status XMLCALL
2082 XML_SetEncoding(XML_Parser p,
2083 const XML_Char *encoding);
2084 </pre>
2086 Set the encoding to be used by the parser. It is equivalent to
2087 passing a non-null encoding argument to the parser creation functions.
2093 </div>
2096 int XMLCALL
2097 XML_SetParamEntityParsing(XML_Parser p,
2098 enum XML_ParamEntityParsing code);
2099 </pre>
2101 This enables parsing of parameter entities, including the external
2102 parameter entity that is the external DTD subset, according to
2105 <ul>
2109 </ul>
2110 </div>
2113 enum XML_Error XMLCALL
2114 XML_UseForeignDTD(XML_Parser parser, XML_Bool useDTD);
2115 </pre>
2117 <p>This function allows an application to provide an external subset
2118 for the document type declaration for documents which do not specify
2119 an external subset of their own. For documents which specify an
2120 external subset in their DOCTYPE declaration, the application-provided
2121 subset will be ignored. If the document does not contain a DOCTYPE
2123 application-provided subset will be parsed, but the
2126 called. The setting of parameter entity parsing, controlled using
2130 <p>The application-provided external subset is read by calling the
2131 external entity reference handler set via <code><a href=
2132 "#XML_SetExternalEntityRefHandler"
2136 <p>If this function is called after parsing has begun, it returns
2139 DTD support, it returns
2145 the document had a DTD with an external subset. This holds true even if
2146 the external entity reference handler returns without action.</p>
2147 </div>
2150 void XMLCALL
2151 XML_SetReturnNSTriplet(XML_Parser parser,
2152 int do_nst);
2153 </pre>
2155 <p>
2156 This function only has an effect when using a parser created with
2159 sets whether or not prefixes are returned with names qualified with a
2161 non-zero, then afterwards namespace qualified names (that is qualified
2162 with a prefix as opposed to belonging to a default namespace) are
2163 returned as a triplet with the three parts separated by the namespace
2164 separator specified when the parser was created. The order of
2165 returned parts is URI, local name, and prefix.</p> <p>If
2167 default manner, URI then local_name separated by the namespace
2168 separator.</p>
2169 </div>
2172 void XMLCALL
2173 XML_DefaultCurrent(XML_Parser parser);
2174 </pre>
2176 This can be called within a handler for a start element, end element,
2177 processing instruction or character data. It causes the corresponding
2178 markup to be passed to the default handler set by <code><a
2182 not a default handler.
2183 </div>
2186 XML_LChar * XMLCALL
2187 XML_ExpatVersion();
2188 </pre>
2191 </div>
2194 struct XML_Expat_Version XMLCALL
2195 XML_ExpatVersionInfo();
2196 </pre>
2198 typedef struct {
2199 int major;
2200 int minor;
2201 int micro;
2202 } XML_Expat_Version;
2203 </pre>
2205 Return the library version information as a structure.
2206 Some macros are also defined that support compile-time tests of the
2207 library version:
2208 <ul>
2212 </ul>
2213 Testing these constants is currently the best way to determine if
2214 particular parts of the Expat API are available.
2215 </div>
2218 const XML_Feature * XMLCALL
2219 XML_GetFeatureList();
2220 </pre>
2222 enum XML_FeatureEnum {
2223 XML_FEATURE_END = 0,
2224 XML_FEATURE_UNICODE,
2225 XML_FEATURE_UNICODE_WCHAR_T,
2226 XML_FEATURE_DTD,
2227 XML_FEATURE_CONTEXT_BYTES,
2228 XML_FEATURE_MIN_SIZE,
2229 XML_FEATURE_SIZEOF_XML_CHAR,
2230 XML_FEATURE_SIZEOF_XML_LCHAR,
2231 XML_FEATURE_NS,
2232 XML_FEATURE_LARGE_SIZE
2233 };
2235 typedef struct {
2236 enum XML_FeatureEnum feature;
2237 XML_LChar *name;
2238 long int value;
2239 } XML_Feature;
2240 </pre>
2243 Expat was configured at compile time. Most applications should not
2244 need to worry about this, but this information is otherwise not
2245 available from Expat. This function allows code that does need to
2246 check these features to do so at runtime.</p>
2251 identifying the feature-test macros Expat was compiled with. Since an
2252 application that requires this kind of information needs to determine
2258 all.</p>
2260 <p>Some features have an associated value. If there isn't an
2262 time, the following features have been defined to have values:</p>
2264 <dl>
2267 character.</dd>
2270 character.</dd>
2272 <dd>The maximum number of characters of context which can be
2275 </dl>
2276 </div>
2279 void XMLCALL
2280 XML_FreeContentModel(XML_Parser parser, XML_Content *model);
2281 </pre>
2286 This function should not be used for any other purpose.
2287 </div>
2289 <p>The following functions allow external code to share the memory
2291 is especially useful for third-party libraries that interact with a
2292 parser object created by application code, or heavily layered
2293 applications. This can be essential when using dynamically loaded
2294 libraries which use different C standard libraries (this can happen on
2295 Windows, at least).</p>
2298 void * XMLCALL
2299 XML_MemMalloc(XML_Parser parser, size_t size);
2300 </pre>
2304 pointer to the memory or NULL on failure. Memory allocated in this
2307 </div>
2310 void * XMLCALL
2311 XML_MemRealloc(XML_Parser parser, void *ptr, size_t size);
2312 </pre>
2320 a pointer to the memory or NULL on failure. On success, the original
2321 block has either been expanded or freed. On failure, the original
2322 block has not been freed; the caller is responsible for freeing the
2323 original block. Memory allocated in this way must be freed using
2326 </div>
2329 void XMLCALL
2330 XML_MemFree(XML_Parser parser, void *ptr);
2331 </pre>
2336 </div>
2338 <hr />
2342 </div>
2343 </body>
2344 </html>