Wireshark mailing list archives
enum or #define?
From: Kaul <mykaul () gmail com>
Date: Sun, 14 Feb 2010 23:21:13 +0200
Which one is better? option 1: #define SSL_HND_HELLO_REQUEST 0 #define SSL_HND_CLIENT_HELLO 1 ... or perhaps, option 2: enum { SSL_HND_HELLO_REQUEST, SSL_HND_CLIENT_HELLO, }; ... and then (in both cases): const value_string ssl_31_handshake_type[] = { { SSL_HND_HELLO_REQUEST, "Hello Request" }, { SSL_HND_CLIENT_HELLO, "Client Hello" }, ? TIA, Y.
___________________________________________________________________________ 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:
- enum or #define? Kaul (Feb 14)
- Re: enum or #define? Jaap Keuter (Feb 14)
- Re: enum or #define? Guy Harris (Feb 15)
- Re: enum or #define? Mike Morrin (Feb 15)
- Re: enum or #define? Guy Harris (Feb 15)
- Re: enum or #define? Jaap Keuter (Feb 14)