On Thu, Dec 25, 2003 at 02:53:00PM -0500, S. Alexander Jacobson wrote:
> I must say, this sort of reply is EXTREMELY DISTURBING.
Why are you shouting?
I find your reply EXTREMELY UNHELPFUL.
> It is ridiculous that one needs to get so intimate
> with implementation issues just to read a file!
It
On Wed, 24 Dec 2003, Hal Daume III wrote:
> one other thing you might find useful is to read it imperatively and then
> use unsafeFreezeArray (i think that's the name) to get a pure array out of
> it. since all you'll be doing is reading, this should work nicely for
> you.
I must say, this sort o
one other thing you might find useful is to read it imperatively and then
use unsafeFreezeArray (i think that's the name) to get a pure array out of
it. since all you'll be doing is reading, this should work nicely for
you.
On Wed, 24 Dec 2003, andrew cooke wrote:
>
> Thanks. I should have
Thanks. I should have added that I will only use the array for reading
once it's created. I don't mind whether creating is lazy or eager (it's
currently eager because I was fighting a space leak, but I think that was
down to some other error).
I don't fully understand how either of the suggesti
(1) use unboxed arrays, otherwise you're wasting too much space with
pointers. that is, unless you need laziness on the elements, which i
don't think you do based on your list
(2) (maybe) use imperative arrays; this will help you ensure that
everything is being evaluated quickly.
On Wed, 24 D
Hi,
I have some code (http://www.acooke.org/andrew/ReadTest.hs) that reads
data from a file (an image in ppm format; example data (256*256 pixels) at
http://www.acooke.org/andrew/test.ppm) and stores it in an array of Word8
values. The aim is to read a file that contains 5000 * 5000 * 3 Word8
va
