From: Edgar Friendly <thelema314@gmail.com>
To: Mike Lin <mlin@mlin.net>
Cc: John Prevost <j.prevost@gmail.com>,
fa.caml@googlegroups.com, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] Batteries 2.0.0 released
Date: Wed, 9 Jan 2013 22:04:30 -0500 [thread overview]
Message-ID: <CAL-jcAnyC-gd90Wb9tXkS-PpJ=_MLqbp5CVERCbtArP_cGew7Q@mail.gmail.com> (raw)
In-Reply-To: <CADxsieYfEuaWwM8dZy_eArMo92VAWqAxPNH=Yy5g4c_PYxMScw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]
Yes, this is exactly what it means.
On Wed, Jan 9, 2013 at 10:01 PM, Mike Lin <mlin@mlin.net> wrote:
> Does this mean that executables compiled with batteries (and not
> Camomile) no longer have intrinsic runtime dependencies on Camomile
> files in certain filesystem locations?
> (glad to see this if so!)
>
> On Tue, Jan 8, 2013 at 8:53 PM, Edgar Friendly <thelema314@gmail.com>
> wrote:
> > There is ... light... unicode support. UTF8 strings are still
> supported,
> > and can be transcoded from and to Latin-1. For anything more complex
> than
> > that, you'll need to use Camomile or some other unicode library. You're
> > right that these modules somehow got omitted from the API documentation;
> the
> > online docs are being regenerated as I write this. The disappearance of
> > UCharParser may have been a mistake; looking back at that commit, it
> looks
> > like it was deleted instead of being modified to fit the removal of
> > camomile. It will probably reappear in batteries 2.1.
> >
> > E.
> >
> >
> > On Tue, Jan 8, 2013 at 8:52 PM, John Prevost <j.prevost@gmail.com>
> wrote:
> >>
> >> On Tuesday, January 8, 2013 10:29:25 AM UTC-5, Edgar Friendly wrote:
> >> > ... the issues with Camomile's data files
> >> {...}
> >> > A complete list of API incompatible changes and new additions is
> >> > available at
> >> >
> >> >
> >> >
> https://github.com/ocaml-batteries-team/batteries-included/wiki/Interfacechanges12
> >> >
> >> > and the new documentation is online at
> >> >
> >> >
> >> >
> http://ocaml-batteries-team.github.com/batteries-included/hdoc2/index.html
> >>
> >> The changes page and your comment above suggest that there's still
> Unicode
> >> character support, but it doesn't seem to be listed in the API
> documentation
> >> (and the UCharParser module is explicitly mentioned as being gone,
> which I
> >> wouldn't expect to be the case if there were still Unicode support.)
> >>
> >> Could you clarify?
> >>
> >> Thanks.
> >>
> >> --
> >> Caml-list mailing list. Subscription management and archives:
> >> https://sympa.inria.fr/sympa/arc/caml-list
> >> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> >> Bug reports: http://caml.inria.fr/bin/caml-bugs
> >
> >
>
[-- Attachment #2: Type: text/html, Size: 3516 bytes --]
next prev parent reply other threads:[~2013-01-10 3:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.zp9JM87TmJwYPvI7w+ikHpyQg7w@ifi.uio.no>
2013-01-09 1:52 ` John Prevost
2013-01-09 4:53 ` Edgar Friendly
2013-01-10 3:01 ` Mike Lin
2013-01-10 3:04 ` Edgar Friendly [this message]
2013-01-08 15:27 Edgar Friendly
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='CAL-jcAnyC-gd90Wb9tXkS-PpJ=_MLqbp5CVERCbtArP_cGew7Q@mail.gmail.com' \
--to=thelema314@gmail.com \
--cc=caml-list@inria.fr \
--cc=fa.caml@googlegroups.com \
--cc=j.prevost@gmail.com \
--cc=mlin@mlin.net \
/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).