tcpdump mailing list archives

automating, or validating DLT_ vs LINKTYPE_ values


From: Michael Richardson <mcr () sandelman ca>
Date: Sun, 24 Jun 2018 14:40:04 -0400

Guy, going through the git commits, I see you did:
     Add LINKTYPE_ values to match new DLT_ values, and update LINKTYPE_MATCHING_MAX.

which I guess was my fault that I forgot to add things.

I will write a file doc/DLT_ALLOCATE_HOWTO.md to explain things, and to
remind myself about pcap-common.c additions.



Questions:
  1) should we have some test case or something that checks that the _MAX
  values are identical?  Perhaps a compile-time test using #error?

  2) should we move the LINKTYPE_ defines to another file, and generate that
  file with a script?
  Should we just generate dlt.h and that new file from a third file (YAML
  or JSON or CSV format...)

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr () sandelman ca  http://www.sandelman.ca/        |   ruby on rails    [





_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Current thread: