wireshark-dev October 2010 archive
Main Archive Page > Month Archives  > wireshark-dev archives
wireshark-dev: Re: [Wireshark-dev] XML dictionary parsing with f

Re: [Wireshark-dev] XML dictionary parsing with flex/bison

From: Hadriel Kaplan <HKaplan_at_nospam>
Date: Sun Oct 17 2010 - 04:33:19 GMT
To: Developer support list for Wireshark <wireshark-dev@wireshark.org>

Afaik, libxml2 is under the MIT license which is not only usable in GPL, but also the same license Lua uses which Wireshark clearly has accepted, fwiw. I thought I saw a libxml dependency, but obviously I'm wrong and I'm not going to add yet another library dependency, that's for sure. (wireshark has plenty as is :)

Isn't the lowest level Glib now 2.4? If so, I can probably make do with the basic glib xml parsing abilities and avoid the newer functions added in 2.16/2.18.

-hadriel

On Oct 16, 2010, at 3:05 PM, Anders Broman wrote:

> Stephen Fisher skrev 2010-10-16 18:58:
>> On Sat, Oct 16, 2010 at 12:40:17PM -0400, Hadriel Kaplan wrote:
>>
>>> or libxml2 which I think is included in wireshark builds (right?),
>> libxml2 is not a requirement to build Wireshark, nor is it even an
>> option.
>>
>>> because I'm not familiar with flex/bison or lex/yacc. But if there's
>>> some specific reason flex/bison should be used, I can go learn how to
>>> use them.
>>>
>>> Is there a reason for using flex/bison for that?
>> Probably historical - it's been around since before XML was thought up:)
>> There may be other reasons that I'm not aware of though.
> If I remember correctly long time ago we had an xml stub(for diameter)
> using libxml but there was a question about the licence not being GPL
> compatible. GLIB's xml parser would be an option but you'll have to use
> GLIB_CHECK_VERSION as it's not available in the lowest version we
> require I think.
> Regards
> Anders
>> ___________________________________________________________________________
>> Sent via: Wireshark-dev mailing list<wireshark-dev@wireshark.org>
>> Archives: http://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>> mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe
>>
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe

___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe