Wireshark mailing list archives
Re: Gaining access to ff_pa_action_codes_ext from other protocols
From: Peter Wu <peter () lekensteyn nl>
Date: Thu, 4 Jun 2020 12:07:51 +0200
On Wed, Jun 03, 2020 at 11:17:01AM -0700, Richard Sharpe wrote:
Hi folks, Some protocols define status values etc in terms of 802.11. I am trying to get the latest changes for IEEE1905 into Wireshark and have an issue where one or more dissector functions needs access to ff_pa_action_codes_ext. What is the best way to handle this? 1. Make it non static and allow the linker to deal with it?
This is common. If it is just within the libwireshark (epan/) library, you do not even need WS_DLL_PUBLIC or similar. Either declare it through a header, or use 'extern value_string_ext ff_pa_action_codes_ext;' in both the user and provider. Kind regards, Peter
2. Provide a function that retrieves a pointer to it? 3. Some other mechanism?
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Gaining access to ff_pa_action_codes_ext from other protocols Richard Sharpe (Jun 03)
- Re: Gaining access to ff_pa_action_codes_ext from other protocols Peter Wu (Jun 04)
- Re: Gaining access to ff_pa_action_codes_ext from other protocols Richard Sharpe (Jun 04)
- Re: Gaining access to ff_pa_action_codes_ext from other protocols Peter Wu (Jun 04)