From: Yoriyuki Yamagata <yoriyuki.y@gmail.com>
To: Berke Durak <berke.durak@gmail.com>
Cc: ocaml-lib-devel@lists.sourceforge.net,
caml-list <caml-list@inria.fr>, Richard Jones <rich@annexia.org>
Subject: Re: ExtLib/Camomile UTF8
Date: Tue, 26 Jan 2010 23:31:06 +0900 [thread overview]
Message-ID: <ace6b6831001260631t32a7b600rc38ba9726d0a879c@mail.gmail.com> (raw)
In-Reply-To: <b903a8570805050255q2534a6c8l4bcc4de38e050cba@mail.gmail.com>
Sorry for answering very old message. I was looking to camomile
related email and found this message.
2008/5/5 Berke Durak <berke.durak@gmail.com>:
> Hello,
>
> A few months ago I submitted a small patch to ExtLib to the UTF8 module,
> adding three small but important functions
>
> - substring
> - output_uchar
> - eof
Camomile do have substring (SubText module) and output_char (This is
done by CharEncoding module). I'm not sure that EoF is required.
The idea behind Camomile is that channels raise End_of_File exception
when no character is available to read. I think today most file does
not use EOF character to signify the end of file. They simply
terminates.
> The patch hasn't been integrated in the ExtLib SVN (I've checked the trunk
> and tags on the SVN at code.google.com).
> As it's actually a patch against Camomile, (at the time I didn't know at the
> time that UTF8 was taken from Camomile),
> Richard Jones suggested that this is where the patch should go.
As I stated, Camomile does have things you suggested. It is different
matter whether Extlib shoud have them. This is the matter for
judgement of Extlib team.
> Also maybe you could host Camomile at
> forge.ocamlcore.org...
What is the benefit of it?
--
Yoriyuki Yamagata
yoriyuki.y@gmail.com
next prev parent reply other threads:[~2010-01-26 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 9:55 Berke Durak
2008-05-14 7:54 ` [Ocaml-lib-devel] " Richard Jones
2010-01-26 14:31 ` Yoriyuki Yamagata [this message]
2010-01-26 16:01 ` Sylvain Le Gall
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=ace6b6831001260631t32a7b600rc38ba9726d0a879c@mail.gmail.com \
--to=yoriyuki.y@gmail.com \
--cc=berke.durak@gmail.com \
--cc=caml-list@inria.fr \
--cc=ocaml-lib-devel@lists.sourceforge.net \
--cc=rich@annexia.org \
/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