On May 5, 2009, at 2:50 PM, Joerg Mayer wrote:
The most trivial being the use of C++-style comments, then there is
the use
of Windows only types (PCHAR, UINT, ...).
You might want to, instead, have a layer that uses standard C types
and GLib types and that calls the AirPcap APIs; at some point I plan
to add channel-listing and channel-changing APIs to libpcap/WinPcap,
and they'll sit atop various OS Wi-Fi channel handling mechanisms, as
well as atop the AirPcap driver, and those APIs will just use standard
C types or types defined by libpcap.
