John Lato wrote:
Another (additional) approach would be to encapsulate unsafeInterleaveIO
within some routine and not let it go out into the wild.
lazilyDoWithIO :: IO a - (a - b) - IO b
It would use unsafeInterleave internally but catch all IO errors within
itself.
I wonder if this is a
Message: 8
Date: Tue, 20 Apr 2010 12:08:36 +0400
From: Daniil Elovkov daniil.elov...@googlemail.com
Subject: Re: [Haskell-cafe] memory needed for SAX parsing XML
To: Haskell-Cafe haskell-cafe@haskell.org
Message-ID: 4bcd6104.50...@googlemail.com
Content-Type: text/plain; charset=ISO-8859-1
Jason Dagit wrote:
On Mon, Apr 19, 2010 at 3:01 AM, Daniil Elovkov
daniil.elov...@googlemail.com mailto:daniil.elov...@googlemail.com
wrote:
Hello haskellers!
I'm trying to process an xml file with as little footprint as
possible. SAX is alright for my case, and I think that's
Hello haskellers!
I'm trying to process an xml file with as little footprint as possible.
SAX is alright for my case, and I think that's the lightest way
possible. So, I'm looking at HaXml.SAX
I'm surprised to see that it takes about 56-60 MB of ram. This seems
constant relative to xml file
On Mon, Apr 19, 2010 at 3:01 AM, Daniil Elovkov
daniil.elov...@googlemail.com wrote:
Hello haskellers!
I'm trying to process an xml file with as little footprint as possible. SAX
is alright for my case, and I think that's the lightest way possible. So,
I'm looking at HaXml.SAX
I'm
