September 2010 - Libraries

Re: [Haskell-cafe] Re: Re: [Haskell] ANNOUNCE: reference 0.1
by Maciej Piechotka 08 Sep '10

08 Sep '10

On Wed, 2010-09-08 at 09:53 +0200, Alberto G. Corona wrote: > Ah, ok. I though that your intention was to restrict the class > definition for the IO monad . Goood. > > > Maybe in the long term, it make sense to include this type class in > some monad related package such is mtl, since references are part of > many user monads. I think also that some default instances can be > defined for transformed monads. > Yes - they can. In fact: instance (MonadTrans t, Monad (t m), Reference r m) => Reference r (t m) where newRef = lift . newRef readRef = lift . readRef writeRef r = lift . writeRef r instance (MonadIO m, Reference r IO) => Reference r m where newRef = liftIO . newRef readRef = liftIO . readRef writeRef r = liftIO . writeRef r > > It is pleasant for me to read and write something like > > > x <- readRef rx > > > rather than > > > x<- readMyMonadRef sx > > > Such generalizatiopns may be also good for extracting more common > patterns among different monads. Actually the primary need was to create mutable single-linked list for iteratee-parsec. I didn't wanted to restrict myself to ST or IO so I choose to add class for them. Regards

1 0

ANNOUNCE: reference 0.1
by Maciej Piechotka 07 Sep '10

07 Sep '10

Reference is class which generalizes references and monads they exists in. It means that IORef, STRef and others can be accessed by common interface. Currently it is of form: class Reference r m where 1. There was a proposal to rename the class to MonadRef or MonadReference. IMHO it would imply m -> r functional dependency and therefore disallow the instances for both MVar IO and IORef IO 2. Should the functional dependencies or type famillies be introduced? Personally I don't think so as I would like to allow all of the following: - IORef IO - MVar IO - IORef (ContT IO) - MVar (ContT IO) Any feedback mostly welcome. Regards PS. Darcs repository will be available soon

2 3

ANNOUNCE: iteratee-parsec 0.0.4
by Maciej Piechotka 06 Sep '10

06 Sep '10

Iteratee-parsec is a library which allows to have a parsec (3) parser in Iteratee monad. It contains 2 implementations: - John Lato's on public domain. It is based on monoid and design with short parsers in mind. - Mine on MIT. It is based on single-linked mutable list. It seems to be significantly faster for larger parsers - at least in some cases - but it requires a monad with references (such as for example IO or ST). The version 0.0.4 is ported to iteratee 0.4. Regards

3 4

ANNOUNCE: countable-1.0
by Ashley Yakeley 06 Sep '10

06 Sep '10

countable: Countable, Searchable, Finite, Empty classes. class Countable, for countable types class AtLeastOneCountable, for countable types that have at least one value class InfiniteCountable, for infinite countable types class Searchable, for types that can be searched over class Finite, for finite types class Empty, for empty types data Nothing, an empty type Also includes these orphan instances: instance (Searchable a,Eq b) => Eq (a -> b) instance (Finite a) => Foldable ((->) a) instance (Finite a) => Traversable ((->) a) instance (Show a,Finite a,Show b) => Show (a -> b) It turns out Searchable includes some infinite types. Specifically, countable implements this: instance (Countable c,Searchable s) => Searchable (c -> s) using the algorithm described here: http://math.andrej.com/2007/09/28/seemingly-impossible-functional-programs/ I would welcome improvements. http://hackage.haskell.org/package/countable-0.1 cabal install countable darcs get http://code.haskell.org/countable/ See also this thread: http://thread.gmane.org/gmane.comp.lang.haskell.cafe/73275

4 5

darcs patch: update for containers-0.4
by shelarcy 06 Sep '10

06 Sep '10

DarcsURL: http://darcs.haskell.org/packages/parallel MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_" --=_ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 1 patch for repository http://darcs.haskell.org/packages/parallel: Mon Sep 6 18:21:47 =93=8C=8B=9E (=95W=8F=80=8E=9E) 2010 shelarcy <shelarc= y(a)gmail.com> * update for containers-0.4 --=_ Content-Type: text/x-darcs-patch; name="update-for-containers_0_4.dpatch" Content-Transfer-Encoding: quoted-printable Content-Description: A darcs patch for your repository! New patches: [update for containers-0.4 shelarcy <shelarcy(a)gmail.com>**20100906092147 Ignore-this: 54be1682179f96eba4313c62e71fc3b6 ] hunk ./parallel.cabal 25 extensions: CPP BangPatterns build-depends: base >=3D 4 && < 5, deepseq >=3D 1.1 && < 1.2, - containers >=3D 0.2 && < 0.4, + containers >=3D 0.2 && < 0.5, array >=3D 0.2 && < 0.4 ghc-options: -Wall = Context: [moved from the GHC testsuite Simon Marlow <marlowsd(a)gmail.com>**20100720090606 Ignore-this: 4c4f0658c08086b5ed7f47c02fe88932 ] = [TAG 3.1.0.0 Simon Marlow <marlowsd(a)gmail.com>**20100720103736 Ignore-this: 8bc739e7ed8cbb14fb1b4bdccd28c034 ] = Patch bundle hash: 5c9329cf6e5b43da65f3994ed81c501eeb2388ec --=_-- .

1 0

darcs patch: update for containers-0.4
by shelarcy 06 Sep '10

06 Sep '10

DarcsURL: http://darcs.haskell.org/packages/deepseq MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_" --=_ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 1 patch for repository http://darcs.haskell.org/packages/deepseq: Mon Sep 6 18:16:49 =93=8C=8B=9E (=95W=8F=80=8E=9E) 2010 shelarcy <shelarc= y(a)gmail.com> * update for containers-0.4 --=_ Content-Type: text/x-darcs-patch; name="update-for-containers_0_4.dpatch" Content-Transfer-Encoding: quoted-printable Content-Description: A darcs patch for your repository! New patches: [update for containers-0.4 shelarcy <shelarcy(a)gmail.com>**20100906091649 Ignore-this: 3c636c18ca1a00910ba4d92860da78b9 ] hunk ./deepseq.cabal 21 library { exposed-modules: Control.DeepSeq build-depends: base >=3D 3 && < 5, = - containers >=3D 0.2 && < 0.4, + containers >=3D 0.2 && < 0.5, array >=3D 0.2 && < 0.4 ghc-options: -Wall } Context: [bump cabal version to 1.6 Simon Marlow <marlowsd(a)gmail.com>**20091120160204 Ignore-this: 55db39b0d7d870248151fcc44d37b007 ] = [bump to 1.1.0.0; add source-repository Simon Marlow <marlowsd(a)gmail.com>**20091120160108 Ignore-this: c15ca7c51d1b8f7ec5ac94ea81466cb1 ] = [Revert naming scheme: DeepSeq->NFData, deepseq->rnf Simon Marlow <marlowsd(a)gmail.com>**20091120160058 Ignore-this: 89225ddb9621dc96e6b8705ac76e82d5 = Also add = deepseq :: a -> b -> b ] = [TAG 1.0.0.0 Simon Marlow <marlowsd(a)gmail.com>**20091117105211 Ignore-this: c48b08cec1bc7e5de55bf3c01b07e01b ] = Patch bundle hash: 989559e0521b2c2d7a9e3f27abfbf7060aaa0bd8 --=_-- .

1 0

unix-compat _impure_ptr link error on windows
by Simon Michael 06 Sep '10

06 Sep '10

unix-compat (all versions) is failing to install for me on windows XP with current haskell platform. It succeeds in a wine shell with current HP. I've attached the log of "cabal install -v3 unix-compat". Best regards, -Simon

2 2

Hackage compilation problem
by Dominique Devriese 06 Sep '10

06 Sep '10

Hi all, I am working on a new package to be released on Hackage (grammar-combinators, release not yet announced). It compiles fine on my system (debian testing, special purpose test user with a pristine ~/.cabal), but the Hackage build log shows the below error message (full version on http://hackage.haskell.org/packages/archive/grammar-combinators/0.1/logs/fa…) It seems this error is caused by a transitive dependency (the random package) requiring two versions of the time package (?), which does not show in that package's .cabal file. I cannot reproduce the problem locally and have no idea what might be causing them. I would much appreciate it if anyone with some more cabal/hackage experience could take a look and comment on the issue. Thanks in advance for any help or comment, Dominique Devriese (...) Warning: This package indirectly depends on multiple versions of the same package. This is highly likely to cause a compile failure. package polyparse-1.4 requires haskell98-1.0.1.1 package uu-parsinglib-2.5.5 requires haskell98-1.0.1.1 package haskell98-1.0.1.1 requires random-1.0.0.2 package haskell98-1.0.1.1 requires random-1.0.0.2 package random-1.0.0.2 requires time-1.1.4 package random-1.0.0.2 requires time-1.2.0.3 (...) /usr/local/bin/ghc --make -package-name grammar-combinators-0.1 -hide-all-packages -fbuilding-cabal-package -i -idist/build -i. -idist/build/autogen -Idist/build/autogen -Idist/build -optP-include -optPdist/build/autogen/cabal_macros.h -odir dist/build -hidir dist/build -stubdir dist/build -package-id MaybeT-0.1.2-604a5b30a99ce43ac16f2d5b237f30f7 -package-id base-4.2.0.2-10bdacb430274706a59728e237e2bfb3 -package-id containers-0.3.0.0-ee442470d8dcc9e45f31677c400c5379 -package-id enumerable-0.0.3-31d1bc40fd7c52b3d83d685e52627d98 -package-id fgl-5.4.2.3-347eeff6011a7f9285c305b00fea7a97 -package-id graphviz-2999.10.0.1-50e6cb683e6a2c39de754bd71e19785e -package-id mtl-1.1.0.2-336254fecf8a77054f76cb33671a5177 -package-id multirec-0.4.1-e036b72652c0c1f66e2511984d48035d -package-id parsec-3.1.0-53d2f726d0bc8967e0f6d7424588dca7 -package-id template-haskell-2.4.0.1-bf08798b1934e4d6a3f903f58e0d5159 -package-id uu-parsinglib-2.5.5-40a637b80a29d05a831a175c3f9a060e -O -Wall Text.GrammarCombinators.Base.Domain (...) <command line>: cannot satisfy -package-id uu-parsinglib-2.5.5-40a637b80a29d05a831a175c3f9a060e: uu-parsinglib-2.5.5-40a637b80a29d05a831a175c3f9a060e is unusable due to missing or recursive dependencies: haskell98-1.0.1.1-ca51ba62fed9074ccb8001cd642eb101 (use -v for more information) (...)

3 3

Crypto-API Final Release Candidate
by Thomas DuBuisson 05 Sep '10

05 Sep '10

To all who have provided feedback on crypto-api: (all BCCed - if you aren't on l(a)h.o ML you won't see the follow-up discussion). I intend to release crypto-api on Hackage Tuesday (Sept07). The proposed final version is on the darcs repo now [1]. I'm very appreciative for all the discussion and design ideas, you can see that many of the ideas have been used. This is the last opportunity for discussion before I upload (targeting 7 Sept). Hopefully I've given enough discussion time without being overly verbose (figured erring on the side of verbosity is best). Recent Changes: * Moved modules to Crypto.* from Data.Crypto.* (ML and IRC comments) * New 'getIVIO' function to get an IV using "getEntropy" then wrapping with the IV constructor. * Regarding the new Crypto.Random Module: * renamed 'generateKeypair' to 'buidKeyPair' for name consistency. * genBytesAI --> genBytesWithEntropy (based on a blog comment) * RandomGenerator --> CryptoRandomGen (based on Duncan's comment on reddit) * SplitableGenerator --> SplittableGen and now "split" can't fail (IRC comment) * newGenIO can't fail (for non-broken generators - broken generators might infinite loop) Likely future changes (please send comments!): * Fix Crypto.Random once a Windows user sends a patch. I never tested it and don't believe I got it right by chance. No (or 'few') Windows users seem to be involved in l(a)h.o discussion / steering. * Once a proposal to rework 'random' and move the CryptoRandomGen class into the 'random' package is out+accepted, I'll remove the related code from Crypto.Random. * a signature class (see ML, supporting non-encrypting algs like DSA): class (Binary k, Serialize k) => Signing k where sign :: k -> L.ByteString -> B.ByteString verify :: k -> L.ByteString -> B.ByteString -> Bool buildSigningKey :: (CryptoRandomGen g) => g -> Either GenError ((k,k), g) Less likely changes: * Expand the BlockCipher class to include mode functions like cbc, ctr, etc (for a performance win). Once I see how big the win is and am convinced we can't optimize to get it without bloating the class then I might add them to the class and provide default instances pointing at Crypto.Modes implementations. Not wanting to be a tyrant, here are some other thoughts people have brought up for discussion (which you can assume I don't like for this library, but some made me stop to think): * Using a data type instead of class for AsymCipher (see ML) * Using MPTC and allowing CryptoRandomGen instances to control the generated type (see reddit). This might be proposed for the reworked RandomGen class, but not likely for CryptoRandomGen. * Have a data type allowing named algorithms (data HashName = MD5 | SHA1 | SHA256 | ... | OtherHash String) include a new class routine (hashName :: dsgt -> HashName) (see ML 'cryptohash' thread) * Unified class for stream ciphers and other streaming algorithms (ex: compression) (ML) * use a semantics for BlockCipher and Hash that doesn't require blockSized inputs (see my original crypto overhaul e-mail which detailed 3 possible semantics) * a 'strength' field for each hash and cipher (also mine, but decide it would be more likely for absurd misuse than any type of correct use) * a "Key" class to which all Cipher class keys would belong. Rejected for "over typeclass-ification", no real benefit. Other TODO: * Crypto.Padding still needed * Expand test suite to other hashes, more test of current hashes, more algorithm specific tests (perhaps most notably, block ciphers). Contributers feel free to make more Test.* modules, perhaps one for each algorithm? * Expand test suite to include more properties (an encrypt . decrypt = id property of some sort? A stream cipher property checking correct operation for streams feed 1 byte at a time vs multi-byte? etc). * Improve benchmarks, use CryptoRandomGen class in benchmark. Yes, some of these changes means the version number will be inflating somewhat rapidly, but it will mostly be added functionality so most packages won't have to change anything be remain compatible (advise you selectively import: "import Crypto.Foo (...)"). Cheers, Thomas [1] code.haskell.org/~tommd/crypto

1 0

Crypto-API is stabilizing
by Thomas DuBuisson 05 Sep '10

05 Sep '10

All, Crypto-API - a unified interface to which I hope hash and cipher algorithms will adhere - has recently gotten a reasonable amount of polish work. I continue to welcome all comments! A blog on its current interface is online [1] as are darcs repositories of the crypto-api package [2]. Recent changes includes added block cipher modes, platform-independent RNG, tests, a simplistic benchmark framework, and minor tweaks of the classes. I've made experimental hash, block cipher and stream cipher instances. Almost no optimizations have been made as of yet! Thanks to everyone for their past comments! I have made numerous changes based on input received. If you feel I didn't respond properly to your suggestion then please ping me again - this is purely a spare time effort and things do fall through the cracks. Cheers, Thomas [1] http://tommd.wordpress.com/2010/08/23/a-haskell-api-for-cryptographic-algor… [2] http://community.haskell.org/~tommd/crypto/ (If you're wondering why you're BCCed its probably because you worked on a crypto-related Haskell package)

2 5