Hi,
It was I who had brought up this topic about a week back (
http://www.wireshark.org/lists/wireshark-dev/200903/msg00261.html) and in general it seems to me that it is a bad idea to use any Glib functionality which has introduced after Glib 2.4 (there was another mail earlier today about the same).
I am going to fall back to the old code which I had written (copied from the parser generator for Diameter dictionary). I don't think it is a very straight forward way of handling it, but it seems to be the "cleanest" option for now.
If more and more developers want to use XML configuration files, perhaps it might be good to introduce a dependency anyway... any small, cross-platform XML parsing library (even if it a subset of XML) with a compatible license should do.
Regards,
Abhik.
2009/3/30 Anders Broman
<a.broman@xxxxxxxxx>
Hi,
No currently there is no
XML parsing library used, the diameter dissector parses XML to load the AVP:s
But I don’t think
it’s a general xml parser. A similar approach could be used depending on
your needs.
Adding a XML library to
the current project needs to be discussed I suppose, using GMarkupParser
as per your previous
mail might be an option (some
one else suggested that as well) the drawback is that it’s only available
in recent
versions of glib, I’ve
no idea if it limited to glib’s needs or if it’s a general XML
parser. Using Glib might be more appealing
than adding another
library however. Comments any one?
Regards
Anders
for my project, i have to use a parser,
and i have several questions :
- Should i create a new project to modify
th edependency of the project ?
- Should i use Tinyxml to parse my XML
files or, is there already a parser in wireshark ?
-
how can i use this parser if there is already one ?
Can you answer to my questions please
because the dead line of my project come quickly
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
