> If the representation is simple enough, you might consider accessing > the database via C ... > > Of course, Binary or Native would be easier, but the start-up time > for a large database might be a problem. In fact, Binary allows you to process the data directly from the disk rather than hauling it all into memory. This eliminates start-up time altogether. What's more, provided the file is used read-only, you can use pure lazy functions to read the data, rather than having to sequence everything through the IO monad. (And of course for efficiency, the implementation of Binary is written largely in C, via the GreenCard preprocessor for Haskell.) Malcolm [EMAIL PROTECTED] Dr Malcolm Wallace (functional programming research) +44 1904 434756 Department of Computer Science, University of York, YORK YO1 5DD, U.K. ------------------------------------http://www.cs.york.ac.uk/~malcolm/
- Re: Binary files in Haskell Timothy Robin BARBOUR
- Re: Binary files in Haskell Jerzy Karczmarczuk
- Re: Binary files in Haskell Malcolm Wallace
- Re: Binary files in Haskell S. Alexander Jacobson
- Re: Binary files in Haskell Martin Norbäck
- Re: Binary files in Haskell Charles Martin
- Re: Binary files in Haskell Simon L Peyton Jones
- Re: Binary files in Haskell Malcolm Wallace
- Re: Binary files in Haskell Steve Roggenkamp
- Re: Binary files in Haskell Timothy Robin BARBOUR
- Re: Binary files in Haskell Malcolm Wallace
- Re: Binary files in Haskell Timothy Robin BARBOUR
- Re: Binary files in Haskell Malcolm Wallace
- binary files in haskell Timmy Douglas
- Re: binary files in haskell Sven Panne
- Re: binary files in haskell John Meacham
- Re: binary files in haskell Sven Panne
- Re: binary files in haskell Timmy Douglas
- RE: binary files in haskell Simon Marlow
- Re: binary files in haskell Olaf Chitil
- Re: binary files in haskell Marcin 'Qrczak' Kowalczyk