[Haskell-cafe] Network trouble: what to do?

[Bryan O'Sullivan]

On Wed, Oct 15, 2008 at 6:54 AM, Creighton Hogg <wchogg at gmail.com> wrote:

> Is there a way around this that I just haven't seen, or should I write
> a patch to Network to add an extra constructor to SockAddr and code to
> handle it?

Linux and Windows support Bluetooth sockets, but they have different
ideas of what the address family is called (AF_BTH vs AF_BLUETOOTH).
Less popular platforms are all over the map: some (Solaris) have no
support, others (NetBSD) don't use sockets for Bluetooth. I don't
think that a patch to Network.Socket is the way to go for this, since
it won't be portable enough. Perhaps a Network.Bluetooth package is in
order to hide all the platform-specific gunk.