Ethereal-dev: Re: [ethereal-dev] cvs commit: ethereal packet-aarp.c

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Gilbert Ramirez <gram@xxxxxxxxxx>
Date: Mon, 04 Oct 1999 08:52:59 -0500
On Sun, Oct 03, 1999 at 11:58:28PM -0700, Guy Harris wrote:
> > Ok, if so, we will have to add many FT_XXX types (e.g. FT_LITTLE_UINTX,
> > FT_BIG_UINTX, FT_NON_C_STRING etc.) and carefully choose the routine
> > arguments...
> 
> The endianness could perhaps be separate from the type.  In most cases,
> the endianness of a given field is fixed, and could be in another field
> of the "header_field_info" structure, and not have to be passed as an
> argument.

Yes. I'm restructuring the header_field_info struct, and for integers,
I'm going to have a separate field denoting in which base the field should
be displayed (decimal, hex, octal, binary). I could bitwise-OR that
with a flag indicating endianness.

> display filters knows what to do with the string (Do we support string
> comparisons in display filters?  If not, we will probably want to,
> eventually.)

Not yet, but we will. I want to have string comparisons for equivalence
and regexes:

	some.string == "hostname"
	some.string =~ /hostname/

and as you suggested:
	ip.proto == "IP"

--gilbert