From: "Nathaniel Gray" <n8gray@gmail.com>
To: "Jon Harrop" <jonathandeanharrop@googlemail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] New Ocaml Plug-in for NetBeans
Date: Tue, 9 Sep 2008 00:50:35 -0700 [thread overview]
Message-ID: <aee06c9e0809090050i4aa95d48v8e083f54c06a5fa5@mail.gmail.com> (raw)
In-Reply-To: <200809090843.33190.jon@ffconsultancy.com>
On Tue, Sep 9, 2008 at 12:43 AM, Jon Harrop
<jonathandeanharrop@googlemail.com> wrote:
> On Tuesday 09 September 2008 06:31:51 you wrote:
>> Sure, I had the same thought, but gzip already exists, doesn't require
>> approval from INRIA, and .gz is easily read in just about any language
>> (including OCaml). Once the .annot files are smaller than the source
>> files I'm completely willing to generate them all the time.
>
> I think you will find that GZip is orders of magnitude less efficient that the
> approach I suggested and too slow to be useful in this case.
>
> For example, gzipping and unzipping the .annot files from the 4kLOC core of
> Smoke takes 0.5s. So GZip is too slow for interactive use even on this tiny
> code base.
Why would you want to unzip more than one .annot file during
interactive use? If I query the type of some token foo in bar.ml I
only need to read from bar.annot.gz, not all the files in the project.
The biggest .annot file I have lying around is from a 40KB source
file. It's about 270KB before gzip, 30KB after. According to "time"
it takes 0.009 seconds to gunzip on my MacBook Pro. I'd say that's
plenty fast enough to be useful, even if your machine isn't quite as
snappy as mine.
I don't dispute that a more efficient encoding than gzip can be found,
but good luck convincing anybody at INRIA to work on it. ;^)
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
next prev parent reply other threads:[~2008-09-09 7:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 8:46 hmf
2008-08-20 6:29 ` Maxence Guesdon
2008-08-20 14:38 ` Richard Jones
2008-08-22 6:34 ` Maxence Guesdon
2008-08-20 16:32 ` Jon Harrop
2008-08-22 6:41 ` Maxence Guesdon
2008-09-07 23:31 ` Nathaniel Gray
2008-09-08 1:10 ` Jon Harrop
2008-09-09 5:31 ` Nathaniel Gray
2008-09-09 7:43 ` Jon Harrop
2008-09-09 7:50 ` Nathaniel Gray [this message]
2008-08-27 20:24 ` kirillkh
2008-09-02 6:49 ` Maxence Guesdon
-- strict thread matches above, loose matches on Subject: below --
2008-07-26 12:44 hmf
2008-07-26 12:01 hmf
2008-07-26 12:25 ` Erik de Castro Lopo
2008-07-26 15:37 ` Jon Harrop
2008-07-26 9:18 hmf
2008-07-26 9:22 ` Richard Jones
2008-07-26 9:02 hmf
2008-07-26 9:19 ` Richard Jones
2008-07-28 9:58 ` Florian Hars
2008-07-26 10:03 ` Erik de Castro Lopo
2008-07-26 11:40 ` Jon Harrop
2008-07-26 12:07 ` Erik de Castro Lopo
2008-07-26 15:22 ` Jon Harrop
2008-07-29 14:16 ` Damien Doligez
2008-07-29 14:30 ` Lukasz Stafiniak
2008-07-29 18:01 ` Jean-Christophe Filliâtre
2008-09-07 21:39 ` Nathaniel Gray
2008-07-26 11:42 ` Jon Harrop
2008-07-22 11:14 adonis28850
2008-07-23 8:42 ` hmf
2008-07-23 8:50 ` adonis28850
2008-07-25 23:56 ` Jon Harrop
2008-07-26 0:24 ` Erik de Castro Lopo
2008-07-26 2:57 ` Jon Harrop
2008-07-26 12:25 ` Romain Beauxis
2008-07-26 9:09 ` Richard Jones
2008-07-28 17:25 ` Pal-Kristian Engstad
2008-07-28 19:25 ` Jon Harrop
2008-07-26 18:12 ` adonis28850
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=aee06c9e0809090050i4aa95d48v8e083f54c06a5fa5@mail.gmail.com \
--to=n8gray@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jonathandeanharrop@googlemail.com \
/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