changeset 24628:52c5daee05c0

Why #if 0\n#define something when you can just #undef it?
author Elliott Sales de Andrade <qulogic@pidgin.im>
date Thu, 11 Dec 2008 04:07:29 +0000
parents 55b7371eadf4
children 662fdd4836aa
files libpurple/protocols/qq/packet_parse.c
diffstat 1 files changed, 2 insertions(+), 4 deletions(-) [+]
line wrap: on
line diff
--- a/libpurple/protocols/qq/packet_parse.c	Thu Dec 11 04:03:27 2008 +0000
+++ b/libpurple/protocols/qq/packet_parse.c	Thu Dec 11 04:07:29 2008 +0000
@@ -32,11 +32,9 @@
 /* note:
  * 1, in these functions, 'b' stands for byte, 'w' stands for word, 'dw' stands for double word.
  * 2, we use '*cursor' and 'buf' as two addresses to calculate the length.
- * 3, change '0' to '1', if want to get more info about the packet parsing. */
+ * 3, change 'undef' to 'define' to get more info about the packet parsing. */
 
-#if 0
-#define PARSER_DEBUG
-#endif
+#undef PARSER_DEBUG
 
 /* read one byte from buf,
  * return the number of bytes read if succeeds, otherwise return -1 */