Wireshark-dev: Re: [Wireshark-dev] capture_file* in dissector code
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Evan Huus <eapache@xxxxxxxxx>
Date: Wed, 13 Nov 2013 09:19:11 -0500
What does "more generic" mean in this context?

On Nov 13, 2013, at 8:15 AM, mmann78@xxxxxxxxxxxx wrote:

I was looking at making the "Decode As" functionality more generic, but my current solution involves having dissectors handle a callback function that passes in a capture_file* as an argument.  Is that valid or does it cross library boundaries creating unwanted dependencies?
___________________________________________________________________________
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