Ethereal-dev: Re: [Ethereal-dev] wierd behaviour of Resolve Name

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

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Thu, 12 Feb 2004 17:54:32 -0800

On Feb 12, 2004, at 5:26 PM, Ulf Lamping wrote:
but: this will enable the function, until *all* three resolution flags are set. 

Yes.
That's exactly what I intended - if any of the resolution flags are *NOT* set, the function is enabled, because, if any of them aren't set, there are names that might not be resolved. If all of them *are* set, presumably all the names that can be resolved are resolved. 


I think:

     cf->current_frame != NULL && (g_resolv_flags & RESOLV_ALL_ADDRS));
would be better, as this will enable this function, when at least one of the flags is set.
...but it won't enable the function if *none* of them are set, and it *will* enable it if *all* of them are set.