summaryrefslogtreecommitdiff
path: root/doc/README.developer
diff options
context:
space:
mode:
authorGerald Combs <gerald@wireshark.org>2013-09-03 18:50:17 +0000
committerGerald Combs <gerald@wireshark.org>2013-09-03 18:50:17 +0000
commitb5e4fd5a012193853dd32d149cad7969305e4a58 (patch)
tree74e5674ca62d956078fe67a6e8d8b39399a29ab7 /doc/README.developer
parent4a226911daad922dcdd4e5fc0cdbee626493ee28 (diff)
downloadwireshark-b5e4fd5a012193853dd32d149cad7969305e4a58.tar.gz
Document the current state of naming in ui/qt. Say it's OK to use C++
comments in C++ code. svn path=/trunk/; revision=51739
Diffstat (limited to 'doc/README.developer')
-rw-r--r--doc/README.developer9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/README.developer b/doc/README.developer
index 0581df56be..4c5a85307c 100644
--- a/doc/README.developer
+++ b/doc/README.developer
@@ -72,10 +72,11 @@ different compilers; here are some rules for writing code that will work
on multiple platforms.
Don't use C++-style comments (comments beginning with "//" and running
-to the end of the line); Wireshark'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).
+to the end of the line) in C code. Wireshark'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). C++-style comments can be
+used in C++ code, of course.
In general, don't use C99 features since some C compilers used to compile
Wireshark don't support C99 (E.G. Microsoft C).