Hi Martin,
Le mer. 17 oct. 2018 à 21:51, Martin Mathieson via Wireshark-dev <
wireshark-dev@wireshark.org> a écrit :
> Hi,
>
> I would like to be able to show, for the generated dissectors, the version
> of the protocol. For 3GPP protocols, in theory they are
> backwards-compatible, but not at t
On Thu, Oct 04, 2018 at 12:17:31PM -0700, Guy Harris wrote:
> On Oct 4, 2018, at 11:19 AM, Guy Harris wrote:
>
> > doesn't help, and there doesn't appear to *be* any documentation for the
> > alleged "CMAKE_C_FLAGS_*" flags.
>
> What they meant was "CMAKE__FLAGS_* flags".
>
> And I've filed a
Hi,
I would like to be able to show, for the generated dissectors, the version
of the protocol. For 3GPP protocols, in theory they are
backwards-compatible, but not at this point in the NR(5G) standards.
So for the 3GPP .asn files, the first line might be e.g.
-- 3GPP TS 38.331 V15.3.0 (2018
Hi Richard,
May be a good idea to open a issue on bugtracker for don't forget...
On Wed, Oct 17, 2018 at 12:00 AM Richard Sharpe
wrote:
> Hi folks,
>
> During testing of my changes to add support for Range Strings to the
> Lua support I found that there was a serious bug in the support for
> va
On Tue, Oct 16, 2018 at 9:28 PM Richard Sharpe
wrote:
> Hi folks,
>
> I see that there is a val64_structure and various functions using it
> there seems to be no ran64_string (the 64-bit version of
> range_strings).
>
> Is that because no one has needed it until now?
>
I think, it is because no o
