Re: [Wireshark-dev] hfinfo.string const initializer / change VALS by preference ?

2010-06-19 Thread Harald Welte
Hi Jakub, thansks a lot for your help. On Fri, Jun 18, 2010 at 10:48:07AM +0200, Jakub Zawadzki wrote: > 1/ You can use value_string_ext (and or hfinfo.display with BASE_EXT_STRING) > > static const value_string vs_vendor0[] = { ... }; /* pref_vendor == 0 */ > static const value_string vs_

Re: [Wireshark-dev] hfinfo.string const initializer / change VALS by preference ?

2010-06-18 Thread Jakub Zawadzki
Hi, On Fri, Jun 18, 2010 at 09:35:02AM +0200, Harald Welte wrote: > As part of the OpenBSC project, I've been working on a dissector for the GSM > A-bis OML protocol. One of the problems with this protocol is that it only > specifies a set of common functions which are then extended by each > ve

[Wireshark-dev] hfinfo.string const initializer / change VALS by preference ?

2010-06-18 Thread Harald Welte
Hi! As part of the OpenBSC project, I've been working on a dissector for the GSM A-bis OML protocol. One of the problems with this protocol is that it only specifies a set of common functions which are then extended by each vendor/implementor. This starts with the message type. There are some