Network problem with ghc on WinXP
sof at galois.com
Thu Jan 29 08:05:05 EST 2004
Me neither; I'm guessing it goes back to the days when
PortNumber used to be a type synonym (and synonyms
could/had to be exported with (..).)
----- Original Message -----
From: "Simon Marlow" <simonmar at microsoft.com>
To: "Sigbjorn Finne" <sof at galois.com>; "robin abraham"
<abraharo at cs.orst.edu>
Cc: <glasgow-haskell-users at haskell.org>
Sent: Thursday, January 29, 2004 03:33
Subject: RE: Network problem with ghc on WinXP
> Is there a reason not to export PortNumber abstractly? I can't think of
> one off-hand.
> > -----Original Message-----
> > From: glasgow-haskell-users-bounces at haskell.org
> > [mailto:glasgow-haskell-users-bounces at haskell.org] On Behalf
> > Of Sigbjorn Finne
> > Sent: 29 January 2004 06:37
> > To: robin abraham
> > Cc: glasgow-haskell-users at haskell.org
> > Subject: Re: Network problem with ghc on WinXP
> > Hi there,
> > looks like a network byte-order vs host byte-order gotcha.
> > Never use the PortNum constructor, but declare 'portnum'
> > to have type PortNumber and simply drop the use of PortNum
> > in your code alltogether. Alternatively, use intToPortNumber
> > to translate between Int and PortNumber.
> > hth
> > --sigbjorn
More information about the Glasgow-haskell-users