I'll check at them.

        fulvio

> -----Original Message-----
> From: Guy Harris [mailto:[EMAIL PROTECTED]
> Sent: venerdi 11 aprile 2003 9.58
> To: [EMAIL PROTECTED]
> Subject: Re: [WinPcap-users] pcap_compile_nopcap
> 
> 
> On Fri, Apr 11, 2003 at 09:33:33AM +0200, Dries Decock wrote:
> > I've a question about the deprecated fuctions
> 
> The "deprecated" and "discouraged" items in the function list have a
> number of problems, which probably need to be cleaned up:
> 
>       Unless there's a way to open a "dead" pcap_t with "pcap_open()",
>       "pcap_open_dead()" cannot be deprecated in favor of
>       "pcap_open()".
> 
>       If "pcap_findalldevs()" is deprecated in favor of
>       "pcap_findalldevs_ex()", other functions should be deprecated in
>       favor of "pcap_findalldevs_ex()", not in favor of
>       "pcap_findalldevs()".
> 
>       "pcap_dump()" cannot be used instead of "pcap_file()" -
>       "pcap_dump()" deals with writing savefiles, while "pcap_file()"
>       deals with getting at the "FILE *" for the file from which a
>       savefile is being read.
> 
>       "pcap_fileno()" can't be deprecated in general, as it's still
>       useful on UNIX (and potentially necessary on UNIX, if you're
>       going to use a "select()"/"poll()" loop), although it
>       *can* be designated a UNIX-only function (in fact, perhaps it
>       should be removed from WinPcap, by putting #ifndef WIN32/#endif
>       around it).
> 
> 
> ==================================================================
>  This is the WinPcap users list. It is archived at
>  http://www.mail-archive.com/[EMAIL PROTECTED]/
> 
>  To unsubscribe use 
>  mailto: [EMAIL PROTECTED]
> ==================================================================


==================================================================
 This is the WinPcap users list. It is archived at
 http://www.mail-archive.com/[EMAIL PROTECTED]/

 To unsubscribe use 
 mailto: [EMAIL PROTECTED]
==================================================================

Reply via email to