caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nathaniel Gray" <n8gray@gmail.com>
To: "Jon Harrop" <jonathandeanharrop@googlemail.com>
Cc: "Maxence Guesdon" <maxence.guesdon@inria.fr>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] New Ocaml Plug-in for NetBeans
Date: Mon, 8 Sep 2008 22:31:51 -0700	[thread overview]
Message-ID: <aee06c9e0809082231j5bfc1bbfg50cacc4167baff55@mail.gmail.com> (raw)
In-Reply-To: <200809080210.57000.jon@ffconsultancy.com>

On Sun, Sep 7, 2008 at 6:10 PM, Jon Harrop
<jonathandeanharrop@googlemail.com> wrote:
> On Monday 08 September 2008 00:31:47 Nathaniel Gray wrote:
>> In fact, gzip does a pretty fine job of optimizing .annot files.  The
>> source file this .annot came from is 15K, the .annot file is 78K, and
>> gzipping it gets it down to 9K.
>
> Tokenizing that .annot format by simply mapping each string onto a unique
> token and writing out the mapping first will shrink such files enormously
> whilst still being easily dissected from any language. Moreover, the benefit
> is super-linear...

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.

Cheers,
-n8

-- 
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->


  reply	other threads:[~2008-09-09  5:31 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 [this message]
2008-09-09  7:43           ` Jon Harrop
2008-09-09  7:50             ` Nathaniel Gray
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=aee06c9e0809082231j5bfc1bbfg50cacc4167baff55@mail.gmail.com \
    --to=n8gray@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=jonathandeanharrop@googlemail.com \
    --cc=maxence.guesdon@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).