October 2007 - Libraries

X11 package
by Don Stewart 07 Oct '07

07 Oct '07

I've taken over maintainership of the X11 package, as we need it for xmonad. The previous maintainer was libraries@. Let me know if you've any problems with this. -- Don

1 0

Proposal: Fix abstract unix sockets (#1699)
by Lennart Kolmodin 05 Oct '07

05 Oct '07

Hi, I've added proposal #1699 to fix abstract unix sockets on Linux for the network library. The patch is so far only tested under Linux (2.6.15), but should not affect Windows or other OSes which does not have AUS. >From the darcs patch comment: Abstract Unix Socket paths begin with a zero, are not zero terminated and needs accurate socklen calculation. Thus this patch, on linux: * Calculates the exact size of sockaddr. * Pokes sockaddr correctly wrt aus. Also, due to much more socklen usage: * Switch Network.Socket to use CSockLen instead of CInt. * Cleanup surrounding code. Cheers, Lennart Kolmodin -- "The only thing that interferes with my learning is my education." -- Albert Einstein

2 2

Control.Monad, Control.Applicative vs. Data.Foldable, Data.Traversable
by Henning Thielemann 01 Oct '07

01 Oct '07

What is the reason for some of the standard type classes being in 'Data' folder and some in 'Control'? Since, say 'Reader' is a monad, an applicative thing, an arrow and an instance of other classes - why is it located in Control.Monad? Why not Data.Reader? I find it reasonable to have a directory for concrete data types and one directory for classes. Currently I cannot see, why the Reader data type is in Monad, Monad is in Control, but Foldable class is in Data, together with List, Tree and other concrete data types.

1 0