May 2006 - Libraries - Haskell.org

Re: ByteStrings and the ram barrier
by dons＠cse.unsw.edu.au 14 May '06

14 May '06

kahl: > > > > After tuning the chunk size to the cache size, the filter 'e' test now > > runs in: > > 4.52 minutes, 53% cpu. > > With respect to the original comparison, > Ryan Lortie pointed out that ``sed'' is an unfair comparison, > and ``tr'' would be more appropriate. Hi! Good idea, I always forget about tr. Here's the result: manzano$ time tr -d e < /home/dons/data/10G > /dev/null tr -d e < /home/dons/data/10G > /dev/null 26% cpu 4:34.55 total I'm happy with this, within 6% of C, for a one liner. The Haskell program is: > import System.IO > import Data.Char > import qualified Data.ByteString.Lazy as L > > main = L.hGetContents stdin >>= L.hPut stdout . L.filterNotByte e > where e = fromIntegral . ord $ 'e' -- Don

1 0

[patch] Win32 enchaments
by Esa Ilari Vuokko 12 May '06

12 May '06

Hi Is this really the list for patches? http://darcs.haskell.org/packages/Win32/_darcs/prefs/email says it is. Here's few patches to Win32. First cabal file needed some poking to be usable and boring-control is also nice to have. Main patch brings in file mapping (mmap-style api in Windows) and most of the Time API. There's also some few more enchaments and fixes to warnings etc. I quickly tested that I can get Makefile work too, but I haven't tested it much yet. I also pushed version number so it's possible to use cabal versioning to fail versions without added stuff. Best regards, --Esa Tue May 9 15:35:25 FLE Standard Time 2006 Esa Ilari Vuokko <ei(a)vuokko.info> * Make repo buildable with cabal and add better boring-control Wed May 10 14:18:35 FLE Standard Time 2006 Esa Ilari Vuokko <ei(a)vuokko.info> * Add FileMapping and Time and other tweaks. Upped version to 1.1 Added System.Win32.Time - most of Time api Added System.Win32.FileMapping - file mapping api and helpers Added BY_HANDLE_FILE_INFORMATION and getFileInformationByHandle Added SYSTEM_INFO and getSystemInfo Cleaned up few warnings and bugs Few more cabal tweaks to options Wed May 10 14:25:41 FLE Standard Time 2006 Esa Ilari Vuokko <ei(a)vuokko.info> * Update Makefile and package.conf.in

3 5

network-alt patch
by Dominic Steinitz 07 May '06

07 May '06

Einar, This wouldn't build for me. I've created a patch for configure.ac. May I suggest you try it on your system to check I haven't broken anything? Dominic. BTW I got this but assume it's because I don't have IPv6 support. Running test: Plain TCP IPv6 server @ 10380 > FAILED: user error (no socket to listen on)

2 1

Non-exhaustive pattern in Socket.hsc
by Dominic Steinitz 06 May '06

06 May '06

I'm getting [root@tility pcap]# ./test test: Socket.hsc:(1434,17)-(1523,20): Non-exhaustive patterns in case The problem is caused because pcap_findalldevs is returning an address family value of 17 #define PF_PACKET 17 /* Packet family. */ #define AF_PACKET PF_PACKET and the ghc Family datatype doesn't support it :-( data Family = AF_UNSPEC | AF_UNIX | AF_INET | AF_INET6 | AF_SNA | AF_DECnet | AF_APPLETALK | AF_ROUTE | AF_X25 | AF_AX25 | AF_IPX -- Imported from Network.Socket *Main> map packFamily [AF_UNSPEC,AF_UNIX,AF_INET,AF_INET6,AF_SNA,AF_DECnet,AF_APPLETALK,AF_ROUTE,AF_X25,AF_AX25,AF_IPX] [0,1,2,10,22,12,5,16,9,3,4] I think I have two choices: 1. Amend ghc. I haven't built ghc for a long time. Would I have to build the whole of ghc? I presume I would have to because of dependencies. 2. Use Network.Alt since http://www.cs.helsinki.fi/u/ekarttun/network-alt/doc/Network.Alt.Types.html defines type Family = Int Any advice? What is the long term plan for Network anyway? Thanks, Dominic.

6 6

Unsafe Functions
by Ashley Yakeley 04 May '06

04 May '06

I would like to start a discussion on the role of unsafe functions in Haskell: unsafePerformIO :: IO a -> a unsafeInterleaveIO :: IO a -> IO a unsafeInterleaveST :: ST s a -> ST s a unsafeIOToST :: IO a -> ST s a unsafeIOToSTM :: IO a -> STM a unsafeFreeze, unsafeThaw, unsafePreservingMatrix, unsafeRenderPrimitive perhaps also unsafeForeignPtrToPtr :: ForeignPtr a -> Ptr a (which is already under Foreign.*) hGetContents :: Handle -> IO String (which is lazy rather than unsafe per se) * Do you use these, and what for? * Is there safe functionality that can currently only be obtained with them? * Do you think they should be standardised, and how? I'm thinking the unsafe functions should be moved from System.IO.Unsafe and elsewhere to Unsafe, similar to Foreign.*, to better separate them from "real Haskell" conceptually. Also, I would add: unsafeCoerce :: a -> b -- Ashley Yakeley, Seattle WA WWEWDD? http://www.cs.utexas.edu/users/EWD/

3 5

Cabal and fps merge into base-package
by Einar Karttunen 04 May '06

04 May '06

Hello How is one supposed to handle fps being merged to the base package in a Cabal file? Clearly GHC 6.4 will need to depend on the fps package while with GHC 6.5 such a dependency is superfluous, and actually having fps installed will cause conflicts. What is the right solution? - Einar Karttunen

4 3

Cabal 1.1.4 and a new Cabal-devel mailing list
by Duncan Coutts 02 May '06

02 May '06

=== Cabal 1.1.4 release === Cabal-1.1.4, the version shipped with GHC 6.4.2 is now available to download as a separate tarball: http://haskell.org/cabal/download.html http://haskell.org/cabal/release/cabal-1.1.4/cabal-1.1.4.tar.gz Note that there was some confusion over the version number. If you got a darcs development snapshot in the last few months it will likely have been marked 1.1.4, however it should have been marked 1.1.5. 1.1.4 is the version shipped with GHC 6.4.2 and available as the tarball above. The current darcs development version is 1.1.5. We'll try to avoid such confusion in the future. === New Cabal-devel mailing list === There is also a new cabal-devel(a)haskell.org mailing list for Cabal development discussion including patch review. This is where patches sent via "darcs send" will end up. We welcome anyone to join the list and help discuss ongoing Cabal development or just to keep an eye on what's going in. Sign up here: http://haskell.org/mailman/listinfo/cabal-devel We'd also like to take the opportunity to invite people to get involved in Cabal development, either new features or squashing annoying bugs. It's as simple as: darcs get --partial http://darcs.haskell.org/packages/Cabal # write patch darcs record darcs send People who already commit directly via darcs push are welcome to continue to do so for patches they consider obvious. If they would like some review and feedback then they are welcome to "darcs send" instead and discuss the patch on the mailing list before committing. Note that this new list is not intended to take discussions of Cabal away from the libraries list. Issues affecting users should still go to libraries(a)haskell.org. The intention is to have more discussion and review of Cabal development. Duncan (who is wearing his new Cabal release manager's hat)

1 0

cabal-install, cabal-setup, new world order
by Isaac Jones 01 May '06

01 May '06

Greetings, I've just pushed some recent work by Alson Kemp to the cabal repository. Alson has integrated the cabal-get tool (by Lemmih) and dependencies into the cabal source tree. This brings in a bunch of unwanted dependencies, though, and we'll be working to trim these out in order to make it a manageable size. Another thing is that I changed cabal-get to be called cabal-install, and removed the (never released) old version of cabal-install from the repo. The reason is that the role of cabal-get will expand to include what cabal-install was meant to do. That is, cabal-install will be used for installing groups of inter-dependent packages, whether they are on hackage.haskell.org or on your local machine. It doesn't do that yet, though; it can only install stuff from hackage. Also, Simon pushed his cabal-setup tool. Cabal-setup is basically like a boilerplate Setup.lhs, but smarter. So the Hackage toolchain will look like this: * Cabal is the library / package * cabal-setup is for building / installing one package. It's very simple * cabal-install is for installing a group of packages. It's pretty complex. If you grab the current darcs head of cabal, you should be able to "sudo make install" and get each of these tools. Then copy etc-cabal-install to /etc/cabal-install, and "cabal-install update" to get the list of packages, "cabal-install install helloWorld2" _should_ work. Your milage may vary. In other news, Duncan Coutts has agreed to become the release manager for Cabal, and we're working on a 1.1.4 release now, which will be the version of Cabal that came with ghc 6.4.2. peace, isaac

1 0