URL
https://opencores.org/ocsvn/openrisc/openrisc/trunk
Subversion Repositories openrisc
[/] [openrisc/] [trunk/] [rtos/] [ecos-3.0/] [packages/] [services/] [ezxml/] [current/] [doc/] [ezxml.html] - Rev 786
Compare with Previous | Blame | View Log
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><title>ezXML</title></head>
<body>
<h1>ezXML - XML Parsing C Library</h1>
<h3>version 0.8.5</h3>
<p>
ezXML is a C library for parsing XML documents inspired by
<a href="http://www.php.net/SimpleXML">simpleXML</a> for
PHP. As the name implies, it's easy to use. It's ideal for parsing XML
configuration files or REST web service responses. It's also fast and
lightweight (less than 20k compiled). The latest version is available
here:
<a href="http://prdownloads.sf.net/ezxml/ezxml-0.8.5.tar.gz?download"
>ezxml-0.8.5.tar.gz</a>
</p>
<b>Example Usage</b>
<p>
Given the following example XML document:
</p>
<code>
<?xml version="1.0"?><br />
<formula1><br />
<team name="McLaren"><br />
<driver><br />
<name>Kimi
Raikkonen</name><br />
<points>45</points><br />
</driver><br />
<driver><br />
<name>David
Coultard</name><br />
<points>24</points><br />
</driver><br />
</team><br />
</formula1>
</code>
<p>
This code snippet prints out a list of drivers, which team they drive for,
and how many championship points they have:
</p>
<code>
ezxml_t f1 = ezxml_parse_file("formula1.xml"), team, driver;<br />
const char *teamname;<br />
<br />
for (team = ezxml_child(f1, "team"); team; team = team->next) {<br />
teamname = ezxml_attr(team, "name");<br />
for (driver = ezxml_child(team, "driver"); driver;
driver = driver->next) {<br />
printf("%s, %s: %s\n",
ezxml_child(driver, "name")->txt, teamname,<br />
ezxml_child(driver, "points")->txt);<br />
}<br />
}<br />
ezxml_free(f1);
</code>
<p>
Alternately, the following would print out the name of the second driver
on the first team:
</p>
<code>
ezxml_t f1 = ezxml_parse_file("formula1.xml");<br />
<br />
printf("%s\n", ezxml_get(f1, "team", 0, "driver", 1, "name", -1)->txt);
<br />ezxml_free(f1);
</code>
<p>
The -1 indicates the end of the argument list. That's pretty much all
there is to it. Complete API documentation can be found in ezxml.h.
</p>
<b>Known Limitations</b>
<ul>
<li>
ezXML is not a validating parser.
<br />
</li>
<li>
Loads the entire XML document into memory at once and does not allow for
documents to be passed in a chunk at a time. Large XML files can still
be handled though through <code>ezxml_parse_file()</code> and
<code>ezxml_parse_fd()</code>, which use mmap to map the file to a
virtual address space and rely on the virtual memory system to page in
data as needed.
<br />
</li>
<li>
Does not currently recognize all possible well-formedness errors. It
should correctly handle all well-formed XML documents and will either
ignore or halt XML processing on well-formedness errors. More
well-formedness checking will be added in subsiquent releases.
<br />
</li>
<li>
In making the character content of tags easy to access, there is no
way provided to keep track of the location of sub tags relative to the
character data. Example:
<p>
<code><doc>line one<br/><br />line two</doc></code>
</p>
<p>
The character content of the doc tag is reported as
<code>"line one\nline two"</code>, and <code><br/></code> is
reported as a sub tag, but the location of <code><br/></code>
within the character data is not. The function
<code>ezxml_toxml()</code> will convert an ezXML structure back to XML
with sub tag locations intact.
</p>
</li>
</ul>
<b>Licensing</b>
<p>
ezXML was written by Aaron Voisine and is distributed under the terms of
the <a href="license.txt">MIT license</a>.
</p>
</body>
</html>