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

Put in a note about labels requiring statements following them. 

svn path=/trunk/; revision=4413
This commit is contained in:
Guy Harris 2001-12-17 08:35:09 +00:00
parent d0e97c05e8
commit 1409de29e4
1 changed files with 25 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
doc/README.developer
View File

@ -1,4 +1,4 @@
$Id: README.developer,v 1.43 2001/12/10 06:31:49 guy Exp $
$Id: README.developer,v 1.44 2001/12/17 08:35:09 guy Exp $
This file is a HOWTO for Ethereal developers. It describes how to start coding
a Ethereal protocol dissector and the use some of the important functions and
@ -42,6 +42,28 @@ defined. Also, don't assume you can use "%lld", "%llu", "%llx", or
"%llo" to print 64-bit integral data types - not all platforms support
"%ll" for printing them.
Don't use a label without a statement following it. For example,
something such as
if (...) {
...
done:
}
will not work with all compilers - you have to do
if (...) {
...
done:
;
}
with some statement, even if it's a null statement, after the label.
1.1.2 Name convention.
Ethereal uses the underscore_convention rather than the InterCapConvention for
@ -79,7 +101,7 @@ code inside
is needed only if you are using the "snprintf()" function.
The "$Id: README.developer,v 1.43 2001/12/10 06:31:49 guy Exp $"
The "$Id: README.developer,v 1.44 2001/12/17 08:35:09 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.
@ -89,7 +111,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.43 2001/12/10 06:31:49 guy Exp $
* $Id: README.developer,v 1.44 2001/12/17 08:35:09 guy Exp $
*
* Ethereal - Network traffic analyzer
* By Gerald Combs <gerald@ethereal.com>