Note that C++-style comments shouldn't be used in dissectors.

svn path=/trunk/; revision=1680

1 files changed, 9 insertions, 3 deletions

diff --git a/doc/README.developer b/doc/README.developer
index c786eb19d1..7d3ee2479e 100644
--- a/doc/README.developer
+++ b/doc/README.developer
@@ -1,4 +1,4 @@
-$Id: README.developer,v 1.2 2000/03/01 08:05:49 guy Exp $
+$Id: README.developer,v 1.3 2000/03/02 07:47:20 guy Exp $
 
 This file is a HOWTO for Ethereal developers. It describes how to start coding
 a protocol dissector and the use some of the important functions and variables 
@@ -7,6 +7,12 @@ in Ethereal.
 See also the "proto_tree" file for a more detailed description of the
 protocol tree construction functions.
 
+NOTE: please don't use C++-style comments (comments beginning with "//"
+and running to the end of the line); Ethereal's dissectors are written
+in C, and thus run through C rather than C++ compilers, and not all C
+compilers support C++-style comments (GCC does, but IBM's C compiler for
+AIX, for example, doesn't do so by default).
+
 1. Setting up your protocol dissector code.
 
 This section provides skeleton code for a protocol dissector. It also explains
@@ -40,7 +46,7 @@ code inside
 
 is needed only if you are using the "snprintf()" function.
 
-The "$Id: README.developer,v 1.2 2000/03/01 08:05:49 guy Exp $" in the comment will be updated by CVS when the file is
+The "$Id: README.developer,v 1.3 2000/03/02 07:47:20 guy Exp $" in the comment will be updated by CVS when the file is
 checked in; it will allow the RCS "ident" command to report which
 version of the file is currently checked out.
 
@@ -49,7 +55,7 @@ version of the file is currently checked out.
  * Routines for PROTONAME dissection
  * Copyright 2000, YOUR_NAME <YOUR_EMAIL_ADDRESS>
  *
- * $Id: README.developer,v 1.2 2000/03/01 08:05:49 guy Exp $
+ * $Id: README.developer,v 1.3 2000/03/02 07:47:20 guy Exp $
  *
  * Ethereal - Network traffic analyzer
  * By Gerald Combs <gerald@unicom.net>