2007/2/16, Matthias Clasen <<a href="mailto:mclasen@redhat.com">mclasen@redhat.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, 2007-02-16 at 07:18 +0100, Mikkel Kamstrup Erlandsen wrote:<br><br>><br>> I was thinking about a small c file that implements<br>> serializing and<br>> deserializing the query language in xml and user language. So
<br>> no glib<br>> and no Qt. That way we can all use it. Starting the complete<br>> search is<br>> too much. Let's see if we can pull even serializing and<br>> deserializing
<br>> off decently. Emphasis should be on the right struct / class<br>> for this.<br>><br>> I agree - a fast reference implementation in C could be a good idea.<br>> We are going to need a sax parser though. I don't know how big the
<br>> glib one is - maybe we can rip it out...<br><br>I did not really mean to jump in here, but before you rip something out<br>of glib, consider just using it, please. There is no reason not to use<br>glib. You should be aware that GMarkup is not a full XML parser though,
<br>and may miss things that you need/want.</blockquote><div><br>Yes, I was just tossing ideas about... But why would a c++ indexer targeting qt be using glib? GMarkup doesn't have namespace support afaik and that could be a problem (maybe not)... But I would also hate to write my own sax parser just for this purpose.
<br></div><br></div>Cheers,<br>Mikkel<br>