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
>
>