> In local.glasgow-haskell-bugs, I wrote:
> >Unluckily, this seems to create a new problem: After binding to a
> >specific address, socketPort always returns 0.
>
> net@atlas [16:47:28]> diff -u SocketPrim.old SocketPrim.hsc
> --- SocketPrim.old Thu Jun 7 16:29:47 2001
> +++ Socke
In local.glasgow-haskell-bugs, I wrote:
>Unluckily, this seems to create a new problem: After binding to a
>specific address, socketPort always returns 0.
net@atlas [16:47:28]> diff -u SocketPrim.old SocketPrim.hsc
--- SocketPrim.old Thu Jun 7 16:29:47 2001
+++ SocketPrim.hsc
In local.glasgow-haskell-bugs, you wrote:
>Yes, well spotted. It looks like I mis-translated some of the old code,
>your fix looks right.
Unluckily, this seems to create a new problem: After binding to a
specific address, socketPort always returns 0.
Could someone please check this?
I'll grab a
> The following withObject-modifications
> will have to be applied in several places, I fear. If nobody objects
> I'll wade through SocketPrim.hsc and send a complete diff tomorrow.
> We (Michael & me) are not sure if that's Linux/glibc specific...
> The older stuff surely *might* look broken in t
In local.glasgow-haskell-bugs, you wrote:
>will have to be applied in several places, I fear.
It's less than I thought. Entire patch below.
diff -u SocketPrim.old SocketPrim.hsc
--- SocketPrim.old Thu Jun 7 16:29:47 2001
+++ SocketPrim.hsc Thu Jun 7 16:45:50 2001
@@ -489,18 +489,17 @@
In local.glasgow-haskell-bugs, you wrote:
>>Perhaps, but I can't repeat the bug. Your code fragment appears to work
>>fine here. Which arch/OS, BTW?
The following withObject-modifications
will have to be applied in several places, I fear. If nobody objects
I'll wade through SocketPrim.hsc and s
In local.glasgow-haskell-bugs, you wrote:
>> Suddenly my program which would work fine in 4.08.2 & 5.00 throws
>> a pattern-match failure in SocketPrim/228 when compiled using 5.01.
>> There is the test for AF_INET/AF_UNIX. When catching this in an
>> "otherwise"-rule and printing the passed value
> Suddenly my program which would work fine in 4.08.2 & 5.00 throws
> a pattern-match failure in SocketPrim/228 when compiled using 5.01.
> There is the test for AF_INET/AF_UNIX. When catching this in an
> "otherwise"-rule and printing the passed value, it is 7368, just for
> the record. Is someon
Suddenly my program which would work fine in 4.08.2 & 5.00 throws
a pattern-match failure in SocketPrim/228 when compiled using 5.01.
There is the test for AF_INET/AF_UNIX. When catching this in an
"otherwise"-rule and printing the passed value, it is 7368, just for
the record. Is someone feeling
