From 884ef57f1e4ab2aa1a6b18d78ab563f35cfd7a9f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stig=20Bj=C3=B8rlykke?= Date: Wed, 8 Jul 2009 08:04:30 +0000 Subject: [PATCH] From Kovarththanan Rajaratnam: Update to include the new constraints. svn path=/trunk/; revision=29015 --- doc/README.developer | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/README.developer b/doc/README.developer index e0530484df..ba28b713f0 100644 --- a/doc/README.developer +++ b/doc/README.developer @@ -1696,6 +1696,12 @@ represent unsigned integers, and the FT_INT* variables all represent signed integers; the number on the end represent how many bits are used to represent the number. +Some constraints are imposed on the header fields depending on the type +(e.g. FT_BYTES) of the field. Non integral types (e.g. types that are _not_ +FT_INT* and FT_UINT*) must use 'BASE_NONE', NULL, 0x0' as values for the +'display', 'strings', 'bitmask' fields. The reason is simply that the type +itself implictly defines the nature of 'display', 'strings', 'bitmask'. + display ------- The display field has a couple of overloaded uses. This is unfortunate, @@ -3610,7 +3616,7 @@ boundary is set in stone. static hf_register_info hf[] = { {&hf_cstring, {"C String", "c.string", FT_STRING, BASE_NONE, NULL, 0x0, - "C String", HFILL} + NULL, HFILL} } };