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