ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 3548] Cleanup header_field_info definitions

Date: Wed, 8 Jul 2009 03:18:07 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3548





--- Comment #82 from Stig Bjørlykke <stig@xxxxxxxxxxxxx>  2009-07-08 03:18:06 PDT ---
(In reply to comment #75)
> Created an attachment (id=3285)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3285) [details]
> Enforce new constraints

I don't know if we should enforce all this with asserts.  We do have Lua
scripts and Python bindings which can add fields, and the assert messages are
not easy to understand.

Does this extra checks increase the startup time?


Another constraint I'm unsure about is FT_BOOLEAN with 'display' value 8 and
'bitmask' value 0, which is the value used when BASE_NONE.  I think we should
allow this, as it describes the length (even if it's default).  


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.