aboutsummaryrefslogtreecommitdiffstats
path: root/doc/README.developer
diff options
context:
space:
mode:
authorGerald Combs <gerald@wireshark.org>2002-12-09 03:09:35 +0000
committerGerald Combs <gerald@wireshark.org>2002-12-09 03:09:35 +0000
commitd44e27b17ce10487439f33a4ad78072edc730b96 (patch)
tree17659569f650b873c9b913029d0a51789623679e /doc/README.developer
parentad323ca96f3f2118ecd2d163d57637304cc0a2f2 (diff)
Fix a typo.
svn path=/trunk/; revision=6769
Diffstat (limited to 'doc/README.developer')
-rw-r--r--doc/README.developer8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/README.developer b/doc/README.developer
index 3193f3f439..eeb7007ec6 100644
--- a/doc/README.developer
+++ b/doc/README.developer
@@ -1,4 +1,4 @@
-$Id: README.developer,v 1.65 2002/11/09 08:37:00 guy Exp $
+$Id: README.developer,v 1.66 2002/12/09 03:09:35 gerald 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
@@ -158,7 +158,7 @@ code inside
is needed only if you are using the "snprintf()" function.
-The "$Id: README.developer,v 1.65 2002/11/09 08:37:00 guy Exp $"
+The "$Id: README.developer,v 1.66 2002/12/09 03:09:35 gerald 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.
@@ -168,7 +168,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.65 2002/11/09 08:37:00 guy Exp $
+ * $Id: README.developer,v 1.66 2002/12/09 03:09:35 gerald Exp $
*
* Ethereal - Network traffic analyzer
* By Gerald Combs <gerald@ethereal.com>
@@ -1185,7 +1185,7 @@ The code to add the FID to the tree would be;
The definition of the field already has the information about bitmasking
and bitshifting, so it does the work of masking and shifting for us!
-This also means that you no longer have to crate value_string structs
+This also means that you no longer have to create value_string structs
with the values bitshifted. The value_string for FID looks like this,
even though the FID value is actually contained in the high nibble.
(You'd expect the values to be 0x0, 0x10, 0x20, etc.)