Wireshark · Wireshark-dev: Re: [Wireshark-dev] Routines for registering dissectors with a"portnumber", and looking up dissector

Wireshark-dev: Re: [Wireshark-dev] Routines for registering dissectors with a"portnumber", and

From: Andreas <AndreasSander1@xxxxxxx>

Date: Mon, 20 Dec 2010 20:02:23 +0100

Am 20.12.2010 19:22, schrieb Stephen Fisher:


Using accessor functions to set and get values as in object-oriented
programming instead of directly using the variables would help prevent
problems like this.

Agreed. This helps hiding implementation change at an API interface.Such set of functions should be well defined to keep the names consistent.


--
Andy

References:
- [Wireshark-dev] Routines for registering dissectors with a "port number", and looking up dissectors by "port number", renamed
  - From: Guy Harris
- Re: [Wireshark-dev] Routines for registering dissectors with a "portnumber", and looking up dissectors by "port number", renamed
  - From: news.gmane.com
- Re: [Wireshark-dev] Routines for registering dissectors with a "portnumber", and looking up dissectors by "port number", renamed
  - From: Guy Harris
- Re: [Wireshark-dev] Routines for registering dissectors with a"portnumber", and looking up dissectors by "port number", renamed
  - From: news.gmane.com
- Re: [Wireshark-dev] Routines for registering dissectors with a"portnumber", and looking up dissectors by "port number", renamed
  - From: Stephen Fisher

Prev by Date: Re: [Wireshark-dev] Routines for registering dissectors with a "portnumber", and looking up dissectors by "port number", renamed
Next by Date: [Wireshark-dev] Bugtracking and patches
Previous by thread: Re: [Wireshark-dev] Routines for registering dissectors with a "portnumber", and looking up dissectors by "port number", renamed
Next by thread: Re: [Wireshark-dev] Routines for registering dissectors with a"portnumber", and looking up dissectors by "port number", renamed
Index(es):
- Date
- Thread