From: Warren Harris <warren@metaweb.com>
To: OCaml <caml-list@inria.fr>
Subject: camomile vs netstring
Date: Tue, 7 Apr 2009 12:12:47 -0700 [thread overview]
Message-ID: <D9C84DFD-43E5-46CE-948E-F76919118E52@metaweb.com> (raw)
Can anyone summarize the trade-offs between the Camomile and Netstring
(netconversion) unicode translation libraries? The netconversion
documentation (http://projects.camlcity.org/projects/dl/ocamlnet-2.2.9/doc/html-main/Netconversion.html
) mentions that Camomile implements text strings as int arrays,
whereas it encodes them as packed native strings... so I'm guessing
that Netstring is a win space-wise when random access isn't needed.
However, are there other trade-offs to be aware of -- bugs, other
performance issues, ease of use? Camomile seems to provide a larger
number of conversions, but I have no idea whether these are actually
useful, or simply legacy artifacts.
I think my unicode needs are fairly simple, but then again, maybe
everyone thinks that as they're diving off this cliff. :-)
Warren
--
Warren Harris
warren@metaweb.com
Metaweb Technologies
http://www.freebase.com - An open database of the world’s information.
reply other threads:[~2009-04-07 19:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=D9C84DFD-43E5-46CE-948E-F76919118E52@metaweb.com \
--to=warren@metaweb.com \
--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