Network.Socket endian problem?
rich.neswold at gmail.com
Thu Dec 14 11:05:34 EST 2006
On 12/13/06, Sigbjorn Finne <sof at galois.com> wrote:
> as you've time-consumingly discovered, Network.Socket.HostAddress
> is represented in network byte order (something that's not well
> documented, and a potential trap.)
> You may want to consider using Network.Socket.inet_addr as
> a constructor.
Thanks to everyone for their help and suggestions. I agree, however,
with Tomasz that the address should be in host byte order to the
application. At the very least, the port value and the address should
use the same byte ordering. For now, I'll use inet_addr as a
AIM : rnezzy
ICQ : 174908475
More information about the Glasgow-haskell-users