Re: capture_file* in dissector code

[Evan Huus <eapache () gmail com>]

What does "more generic" mean in this context?

> On Nov 13, 2013, at 8:15 AM, mmann78 () netscape net 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 () 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