osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

add a small section, that code should be warning free 

svn path=/trunk/; revision=21291
This commit is contained in:
Ulf Lamping 2007-03-31 15:32:06 +00:00
parent 4321baacdc
commit b05d384d71
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/README.developer
View File

@ -579,7 +579,7 @@ Wireshark uses the underscore_convention rather than the InterCapConvention for
function names, so new code should probably use underscores rather than
intercaps for functions and variable names. This is especially important if you
are writing code that will be called from outside your code. We are just
trying to keep things consistent for other users.
trying to keep things consistent for other developers.
1.1.5 White space convention.
@ -602,6 +602,15 @@ utility on an existing file. If you run across wildly varying
indentation styles within the same file, it might be helpful to send a
note to wireshark-dev for guidance.
1.1.6 Compiler warnings
You should write code that is free of compiler warnings. Such warnings will
often indicate questionable code and sometimes even real bugs, so it's best
to avoid warnings at all.
The compiler flags in the Makefiles are set to "treat warnings as errors",
so your code won't even compile when warnings occur.
1.2 Skeleton code.
Wireshark requires certain things when setting up a protocol dissector.