Could someone please write a coding style section for the new dissectors and perhaps point to the best example dissector.
The example would match the coding style and use, preferably, a majority of the API. I would then code EXACTLY to that standard. Currently, many of the dissectors I have submitted are having arbitrary white space/style changes made. I completely understand changes, for bugs, API changes, and warnings missed because of cross-platform builds. But I don't understand the need to change FROM a consistent style to some other style. Michael Lum (michael....@starsolutions.com<mailto:michael....@starsolutions.com>) | STAR SOLUTIONS<http://www.starsolutions.com/> | Principal Software Engineer 4600 Jacombs Road, Richmond BC, Canada V6V 3B1 | +1.604.303.2315
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
