<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 1/19/10 9:26 PM, Nikolay Sivov wrote:
<blockquote cite="mid:4B561593.4050902@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
On 1/19/2010 19:36, Jacek Caban wrote:
<blockquote cite="mid:4B55DFA8.9040507@codeweavers.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<pre>Hi <meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1"><b>Nikolay</b>,
> If I'm right then only solution is to link to libxml2 statically from
> each module. Is it an acceptable way?
>
> P.S. having a separate copy of libxml2 allows to tweak its namespace
> support (I believe there's some discussions of that problem in bugzilla).
</pre>
<br>
I think it would be better to avoid using libxml2 for xmllite
implementation. Writing XML parser from scratch is easy and we can
avoid problems with incompatibilities.<br>
<br>
</blockquote>
Hi.<br>
<br>
Actually I don't see (yet) any incompatibilities for xmllite, except
depth security threshold. I'm not very familiar with parsers in general,<br>
could you help me please with some useful links or good examples of
already implemented simple xml parsers (except libxml2 of course) that
you could suggest as good start.<br>
</blockquote>
<br>
We have a very lite, but also very customized, XML parser in
dlls/ntdll/actctx.c. It mixes parsing with interpreting, but it should
give you a good view on how to write such parser.<br>
<br>
Jacek<br>
</body>
</html>