Wireshark mailing list archives

Re: [Wireshark-commits] rev 30579: /trunk/epan/ /trunk/epan/: emem.c

From: Stephen Fisher <steve () stephen-fisher com>
Date: Tue, 20 Oct 2009 13:30:38 -0600


On Oct 19, 2009, at 12:37 PM, Joerg Mayer wrote:

On Mon, Oct 19, 2009 at 11:12:20AM -0400, Jeff Morriss wrote:

Joerg Mayer wrote:

There seems to be an increasing nunmber of variables that ssem to  
be lacking
documentation. How about adding them to the manpage(s)?


These environment variables are targeted mainly at developers looking
at/debugging memory issues.  Do they really belong in the
(user-oriented) man pages?


I don't like undocumented command line options - and the environment  
vars
are something very similar. So in my opinion: Yes :-)


I can see Joerg's point.  If we don't document it in the man pages, we  
need to document it somewhere other than in source code.


Steve

___________________________________________________________________________
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-request () wireshark org?subject=unsubscribe

Current thread:

Re: [Wireshark-commits] rev 30579: /trunk/epan/ /trunk/epan/: emem.c Joerg Mayer (Oct 17)
- Re: [Wireshark-commits] rev 30579: /trunk/epan/ /trunk/epan/: emem.c Jeff Morriss (Oct 19)
  - Re: [Wireshark-commits] rev 30579: /trunk/epan/ /trunk/epan/: emem.c Joerg Mayer (Oct 19)
    - Re: [Wireshark-commits] rev 30579: /trunk/epan/ /trunk/epan/: emem.c Stephen Fisher (Oct 20)
    - Re: [Wireshark-commits] rev 30579: /trunk/epan/ /trunk/epan/: emem.c Jeff Morriss (Oct 20)