Network.Socket endian problem?

[Tomasz Zielonka]

On Wed, Dec 13, 2006 at 03:54:59PM -0600, Mark Hills wrote:
> It does expect the address to be in network byte order instead of host
> byte order, which is usually done using htons and htonl. This seems to
> do what you want (running SUSE 10.1 on an Intel box):

Who agrees with me that it would be nice if network libraries used host
byte order in their interface? Or at least they could use an abstract
data type, whose byte order would be unobservable.

Best regards
Tomasz