Wireshark mailing list archives
capture_file* in dissector code
From: mmann78 () netscape net
Date: Wed, 13 Nov 2013 08:15:12 -0500 (EST)
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 () 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
Current thread:
- capture_file* in dissector code mmann78 (Nov 13)
- Re: capture_file* in dissector code Evan Huus (Nov 13)
- Re: capture_file* in dissector code Jakub Zawadzki (Nov 13)
- Re: capture_file* in dissector code mmann78 (Nov 13)
- Re: capture_file* in dissector code Jakub Zawadzki (Nov 13)
- Re: capture_file* in dissector code mmann78 (Nov 13)
- <Possible follow-ups>
- Re: capture_file* in dissector code mmann78 (Nov 13)
- Re: capture_file* in dissector code Evan Huus (Nov 13)
- Re: capture_file* in dissector code mmann78 (Nov 13)
- Re: capture_file* in dissector code Evan Huus (Nov 13)
- Re: capture_file* in dissector code mmann78 (Nov 13)
- Re: capture_file* in dissector code Evan Huus (Nov 13)