1dc2c7305SBill Fenner TODO list for libpcap 2dc2c7305SBill Fenner======================= 3dc2c7305SBill Fenner 4dc2c7305SBill FennerImportant stuff (to be done before the next release) 5dc2c7305SBill Fenner--------------- 6dc2c7305SBill Fenner 7dc2c7305SBill FennerGeneral 8dc2c7305SBill Fenner 9dc2c7305SBill Fenner- The source files should be better documented. There is no official 100a94d38fSBill Fenner design guideline for what is done where. There should be a common coding 110a94d38fSBill Fenner style (okay, you can guess that by looking at the code) and a guide for 12dc2c7305SBill Fenner what needs to be documented. 13dc2c7305SBill Fenner 14dc2c7305SBill FennerLess urgent items 15dc2c7305SBill Fenner----------------- 16dc2c7305SBill Fenner 17dc2c7305SBill Fenner- Better documentation and cleanup of the interface. I am seeing a few 18dc2c7305SBill Fenner problems at the first glance which needs fixing: 190a94d38fSBill Fenner + not very well suited for interactive programs (think ethereal). There 200a94d38fSBill Fenner should be a way for the application to get a file descriptor which it 210a94d38fSBill Fenner has to monitor and a callback in pcap which has to be called on 220a94d38fSBill Fenner activity (XXX - "pcap_fileno()" handles the first part, although 230a94d38fSBill Fenner "select()" and "poll()" don't work on BPF devices on most BSDs, and 240a94d38fSBill Fenner you can call "pcap_dispatch()" as the dispatch routine after putting 250a94d38fSBill Fenner the descriptor into non-blocking mode) 26dc2c7305SBill Fenner + too many functions. There are a lot of functions for everything which 27dc2c7305SBill Fenner violates the KISS principle. Why do we need pcap_strerror, pcap_perror 28dc2c7305SBill Fenner and pcap_geterr? 29