- Libraries - Haskell.org

Re: Prelude function suggestions
by Henning Thielemann 30 Jul '04

30 Jul '04

On Thu, 29 Jul 2004, Tomasz Zielonka wrote: > On Thu, Jul 29, 2004 at 06:29:52PM +0200, Henning Thielemann wrote: > > Say, you have some stop condition that you want to use in connection with > > unfoldr: > > > > unfoldr (\n -> toMaybe (n<10) (n,n+1)) 0 > > How about using MonadPlus instance for Maybe? It seems a bit clearer to > me. > > unfoldr (\n -> guard (n<10) >> return (n,n+1)) 0 Ok, nice. Though then again I think about falling back to unfoldr (\n -> if n<10 then Just (n,n+1) else Nothing) 0 I just use toMaybe as common abbreviation. If no one needs it, forget it. :-)

1 0

Re: Prelude function suggestions
by Henning Thielemann 29 Jul '04

29 Jul '04

On Thu, 29 Jul 2004, ariep wrote: > > > {- | Compositional power of a function, > > i.e. apply the function n times to a value. -} > > nest :: Int -> (a -> a) -> a -> a > > nest 0 f x = x > > nest n f x = f (nest (n-1) f x) > > nest n f x = iterate f x !! n > > That might render 'nest' somewhat superfluous. What about: nest n f = foldl (.) id (replicate n f) :-) I'm aware of such transcriptions, but most commonly I use the partial application (nest n f) which can't be provided by them. If 'nest' (or maybe renamed to 'compPower') will be added, anyway, I think it should go where (.) is defined. > > {- | Split the list at the occurrences of a separator into sub-list. > > This is a generalization of 'words'. -} > > chop :: (a -> Bool) -> [a] -> [[a]] > > chop p s = > > let (l, s') = break p s > > in l : case s' of > > [] -> [] > > (_:rest) -> chop p rest > > I like 'chop'. It belongs in Data.List, I'd say. Nice that you like it. :-) Will the text processing functions like 'words' and 'lines' go to a module separate from Data.List in future? > > {- | Returns 'Just' if the precondition is fulfilled. -} > > toMaybe :: Bool -> a -> Maybe a > > toMaybe False _ = Nothing > > toMaybe True x = Just x > > Could you give an example to show what makes 'toMaybe' a particularly > useful function? Say, you have some stop condition that you want to use in connection with unfoldr: unfoldr (\n -> toMaybe (n<10) (n,n+1)) 0 Or say you want to implement a function f :: Set (Maybe a) -> Maybe (Set a) where the result is Nothing if any element of the Set is Nothing, and Just the set containing the Just values otherwise: f s = toMaybe (not (Nothing `elementOf` s)) (mapSet fromJust s)

3 2

RE: Prelude function suggestions
by Simon Marlow 29 Jul '04

29 Jul '04

How about: -- | Splits a list into components delimited by separators, where the -- predicate returns True for a separator element. The resulting -- components do not contain the separators. Two adjacent separators -- result in an empty component in the output. eg. -- -- @ -- > split (=='a') "aabbaca" -- ["","","bb","c",""] -- @ split :: (a -> Bool) -> [a] -> [[a]] split p s = case rest of [] -> [chunk] _:rest -> chunk : split p rest where (chunk, rest) = break p s -- | Like 'split', except that sequences of adjacent separators are -- treated as a single separator. eg. -- -- @ -- > tokens (=='a') "aabbaca" -- ["bb","c"] -- @ tokens :: (a -> Bool) -> [a] -> [[a]] tokens p = filter (not.null) . split p 'split' is the same as Python's split. There is already a precedent for using short names in the Data.List module so I think 'split' is the right choice, and 'tokens' is fairly descriptive. Then we have words = tokens isSpace which is quite nice. Unfortunately lines /= split (=='\n') because lines strips off blank lines at the end. So perhaps we do need the third version. Cheers, Simon

7 7

RE: hierarchical libraries documentation index
by Simon Marlow 29 Jul '04

29 Jul '04

On 29 July 2004 14:16, Martin Sjögren wrote: > I think it would be nice to have the docs split up per-package. I.e. > one page for haskell98, one for base, one for unix etc. Of course, > there could be a complete page of everything too, but I find it's a > pain to navigate it because it's so long... Are you talking about splitting up the contents, or the index? Up until the last release, both of these pages used to be per-package. But we found that this was bad because someone looking for a particular module didn't know which package to look in, and the package boundaries are kind of arbitrary. In the future, when an installation probably has lots of 3rd-party packages installed, each with their own documentation, we'll probably need to re-generate the contents and index page each time a new package is installed. If you find it a pain to navigate the combined contents page, then I think the solution is not to split it up, but to make it easier to navigate (a bit of dynamic HTML goes a long way...). Cheers, Simon

4 3

hierarchical libraries documentation index
by Ross Paterson 29 Jul '04

29 Jul '04

How about omitting the modules of the haskell98 package from the Haskell Hierarchical Libraries documentation index? They're not particularly hierarchical, and they're documented elsewhere. Having them in the doc index makes the docs look bad.

3 3

RE: hierarchical libraries documentation index
by Simon Marlow 29 Jul '04

29 Jul '04

On 29 July 2004 11:32, Ross Paterson wrote: > How about omitting the modules of the haskell98 package from the > Haskell Hierarchical Libraries documentation index? They're not > particularly hierarchical, and they're documented elsewhere. > Having them in the doc index makes the docs look bad. Ok by me. Simon

1 0

RE: copyFile function in Haddock, VSHaskell & Cabal
by Simon Marlow 29 Jul '04

29 Jul '04

On 29 July 2004 08:19, Krasimir Angelov wrote: > I have found a bug in CVS Haddock. It uses the > following definition of copyFile function: > > copyFile f = do > s <- readFile (libdir ++ pathSeparator:f) > writeFile (odir ++ pathSeparator:f) s > > (See HaddockHtml.hs) > > This works well for text files but the function fails > when it is used to copy binary files under Windows. > Similar functions are used also in VSHaskell and > Cabal. I propose to add copyFile function to > System.Directory which will take care of binary files. > The function signature is simple: > > copyFile :: FilePath -> FilePath -> IO () > > In the attached file there are two implementations. > The first is a more portable but slower and the second > is GHC specific but is faster. We have a copyFile function in DirectoryExts (hslibs/lang). I've been meaning to move this over to System.Directory for some time. Your version looks fine - please go ahead! Cheers, Simon

1 0

RE: copyFile function in Haddock, VSHaskell & Cabal
by Bayley, Alistair 29 Jul '04

29 Jul '04

It might be worth lifting copyContents too; I've written this and I've seen it in hws-wp. I called it pipe, and in hws-wp it's called squirt. Perhaps something like this (untested!), in System.IO: hPipe :: Handle -> Handle -> Int -> IO () hPipe hFrom hTo bufferSize = do allocaBytes bufferSize bufferedPipe where bufferedPipe buffer = do count <- hGetBuf hFrom buffer bufferSize when (count > 0) $ do hPutBuf hTo buffer count bufferedPipe buffer > -----Original Message----- > From: Krasimir Angelov [mailto:ka2_mail@yahoo.com] > Sent: 29 July 2004 08:19 > To: libraries(a)haskell.org > Subject: copyFile function in Haddock, VSHaskell & Cabal > > I have found a bug in CVS Haddock. It uses the following > definition of copyFile function: > > copyFile f = do > s <- readFile (libdir ++ pathSeparator:f) > writeFile (odir ++ pathSeparator:f) s > > (See HaddockHtml.hs) > > This works well for text files but the function fails when it > is used to copy binary files under Windows. > Similar functions are used also in VSHaskell and Cabal. I > propose to add copyFile function to System.Directory which > will take care of binary files. > The function signature is simple: > > copyFile :: FilePath -> FilePath -> IO () > > In the attached file there are two implementations. > The first is a more portable but slower and the second is GHC > specific but is faster. > > Any suggestions > Krasimir ----------------------------------------- ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************

1 0

copyFile function in Haddock, VSHaskell & Cabal
by Krasimir Angelov 29 Jul '04

29 Jul '04

I have found a bug in CVS Haddock. It uses the following definition of copyFile function: copyFile f = do s <- readFile (libdir ++ pathSeparator:f) writeFile (odir ++ pathSeparator:f) s (See HaddockHtml.hs) This works well for text files but the function fails when it is used to copy binary files under Windows. Similar functions are used also in VSHaskell and Cabal. I propose to add copyFile function to System.Directory which will take care of binary files. The function signature is simple: copyFile :: FilePath -> FilePath -> IO () In the attached file there are two implementations. The first is a more portable but slower and the second is GHC specific but is faster. Any suggestions Krasimir __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail

1 0

RE: Prelude function suggestions
by Simon Marlow 28 Jul '04

28 Jul '04

On 27 July 2004 23:44, ariep(a)xs4all.nl wrote: >> {- | Split the list at the occurrences of a separator into sub-list. >> This is a generalization of 'words'. -} >> chop :: (a -> Bool) -> [a] -> [[a]] >> chop p s = >> let (l, s') = break p s >> in l : case s' of >> [] -> [] >> (_:rest) -> chop p rest > > I like 'chop'. It belongs in Data.List, I'd say. We have something very like this inside GHC, except we call it 'split'. It's very useful for splitting up file paths into components. For comparison, Perl calls it 'split'. In Perl, 'chop' does something different. Python also has a 'split' function that does something similar. Does anyone object to calling it 'split'? Cheers, Simon

8 12