Re: tvbuffs, doc/README.tvbuff should explain it.
Re: strings, we use char* inside the code. We have FT_STRING, and
FT_UINT8_STRING.
I'm working on a FT_STRINGZ which might be finished tonight.
FT_STRING is useful for pulling out a fixed-length string from a packet, or
adding a string
from C code (that is, not have proto_tree_add_item() pull it out for you).
FT_UINT8_STRING is used only in proto_tree_add_item(). That routine pulls the
uint8
from the tvbuff and uses it as the string length, and pulls that many more bytes
from the tvbuff
to represent the string.
When FT_STRINGZ is done, proto_tree_add_item() will search for a terminating NUL
in the
tvbuff, up to a maximum length that is passed in by you as the length parameter,
and use the
string if it finds the terminating NUL.
--gilbert
Craig Rodrigues <rodrigc@xxxxxxxxxxxx> on 08/25/2000 12:18:41 PM
To: ethereal-dev@xxxxxxxx
cc: (bcc: Gilbert Ramirez/Tivoli Systems)
Subject: [ethereal-dev] IIOP dissector
Hi,
I am interested in enhancing the IIOP dissector
to better support IIOP 1.2. Is anybody else
working on this?
Also, I haven't been following ethereal development
in a while...where can I find out about the new tvbuff
stuff?
I may have asked this before, but I have forgotten....
what data structure is used in Ethereal for strings?
Is it OK to use something like a g_string from the
GDK toolkit?
Thanks.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@xxxxxxxxxxxx
