From: Yoriyuki Yamagata <yoriyuki.y@gmail.com>
To: Adrien Nader <adrien@notk.org>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] ucorelib 0.0.2
Date: Sun, 15 Sep 2013 23:59:24 +0900 [thread overview]
Message-ID: <CALdQWQ6adgDti6OFKC+CBfJTX4m13MTLq__ZL=M5hNDactrkeQ@mail.gmail.com> (raw)
In-Reply-To: <20130915143716.GA25809@notk.org>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
2013/9/15 Adrien Nader <adrien@notk.org>
> Can you explain how this relates to Camomile? Is this meant to be a
> replacement at some point in the future?
>
Yes, it is meant to replace Camomile in the future. I think there are
several problems in Camomile.
1. Monolithic. Camomile is a large library. it forces you to install many
encodings even if you want to just, say, use UTF-8. I will brake Camomile
into the pieces. ucorelib will be a core part of such libraries.
2. Not type safe. UTF-8 string exposes internal byte strings. ucorelib
will provide abstract Text data type whose internal data structure is
hidden.
3. Imperative. Camomile mimics OCaml standard strings which are
imperative. Instead, ucorelib and related libraries will be purely
functional.
4. Functor. Camomile uses functor a lot. Unfortunately this seems to
repel the beginners. ucorelib uses the module language essential ways
(code converters are implemented by using first class modules) but for
casual users it does not requires any knowledge of OCaml's module system.
5. Data files. Camomile needs to external data files to start. This
causes a lot of problems. ucorelib does not need external data files.
6. Unicode version. I want to upgrade everything to Unicode 0.6.X, not
0,3,X.
Best,
--
Yoriyuki Yamagata
yoriyuki.y@gmail.com
[-- Attachment #2: Type: text/html, Size: 2106 bytes --]
next prev parent reply other threads:[~2013-09-15 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 13:17 Yoriyuki Yamagata
2013-09-15 14:37 ` Adrien Nader
2013-09-15 14:59 ` Yoriyuki Yamagata [this message]
2013-09-15 15:07 ` Dmitry Grebeniuk
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='CALdQWQ6adgDti6OFKC+CBfJTX4m13MTLq__ZL=M5hNDactrkeQ@mail.gmail.com' \
--to=yoriyuki.y@gmail.com \
--cc=adrien@notk.org \
--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