From: Eric Cooper <ecc@cmu.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] zcat vs CamlZip
Date: Tue, 29 Aug 2006 15:11:06 -0400 [thread overview]
Message-ID: <20060829191106.GA29559@localhost> (raw)
In-Reply-To: <44F48A17.5080005@podval.org>
On Tue, Aug 29, 2006 at 02:40:23PM -0400, Sam Steingold wrote:
> is this a known performance issue with the CamlZip library?
I found the same thing when I was writing approx, so I use a "gunzip"
process with Sys.command. (You can also use open_process_in, but I
just decompress to a temporary file and then reread it. That also
catches corrupt .gz files in a more robust way.)
--
Eric Cooper e c c @ c m u . e d u
next prev parent reply other threads:[~2006-08-29 19:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 18:40 Sam Steingold
2006-08-29 18:54 ` Bardur Arantsson
2006-08-29 19:01 ` [Caml-list] " Florian Hars
2006-08-29 19:15 ` Sam Steingold
2006-08-29 19:48 ` Bárður Árantsson
2006-08-29 19:54 ` [Caml-list] " Gerd Stolpmann
2006-08-29 20:04 ` Gerd Stolpmann
2006-08-30 0:44 ` malc
2006-08-30 0:53 ` Jonathan Roewen
2006-08-29 19:37 ` John Carr
2006-08-29 19:11 ` Eric Cooper [this message]
2006-08-30 6:12 ` [Caml-list] " Jeff Henrikson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060829191106.GA29559@localhost \
--to=ecc@cmu.edu \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).