https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7348
Michael Mann <mmann78@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mmann78@xxxxxxxxxxxx
--- Comment #1 from Michael Mann <mmann78@xxxxxxxxxxxx> 2012-06-11 14:27:12 PDT ---
I found two possible solutions for this:
1. Dissectors should be add/inserted in sorted order. Currently they are just
appended and since plugins are loaded/registered last, they end up last on the
list. Perhaps register.c is keeping the builtins registered in alphabetized
order?
2. Dissectors can be sorted within dissector_table_foreach_handle(). This is
called by tshark when a bad "Decode As" protocol is found, among other places.
I assume #1 is a better solution (although *shark would probably take a hit at
startup), but the question is what to sort on? I originally tried "long name",
but that didn't seem as alphabetized as "short name" (which wasn't perfect
either, but was much better).
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
