From: Edgar Friendly <thelema314@gmail.com>
To: Tiphaine Turpin <Tiphaine.Turpin@irisa.fr>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Batteries Included 1.0.0
Date: Fri, 22 Jan 2010 18:13:22 -0500 [thread overview]
Message-ID: <4B5A3112.4020100@gmail.com> (raw)
In-Reply-To: <4B596486.90103@irisa.fr>
On 01/22/2010 03:40 AM, Tiphaine Turpin wrote:
> Thank you for your work on batteries. Here are a few comments that I
> have, having "migrated" my source code to this new version.
>
I appreciate your taking the time to give feedback.
> First, I appreciate the reduction of dependencies. This makes it much
> more reasonable to share code using batteries.
>
>
Thank you.
> On the negative side, my greatest concern is about outdated
> documentation : I found it very difficult to know what had changed, and
> how to adapt my code. These changes range from the deletion of some
> features
I'm glad you were able to wade through the new codebase and adapt.
> (batteries/ocaml* tools, myocamlbuild.ml, "open in" syntax
> extension, implicit "open Batteries") to minor API changes
I'm not convinced that the batteries/ocaml* tools were useful - can
people weigh in on this?
Ocamlbuild should have a global directory for packages to install their
own tag extensions, allowing most users to omit myocamlbuild.ml files
from their directory.
"Open in" should be replaced soon in ocaml proper, implicit "open
batteries" seems a bad idea IMHO.
> (naming of
> Standard, Data, Shell modules,
Intentional - flattened structure
> no more Different_list_size exception,
Intentional - too many exceptions.
> no more Queue.enum...).
Should be fixed now, a point release should come out within the week.
> Also, there seems to be a packaging bug which
> requires using -thread in the ocamlfind command.
>
Needs fixing. Added to issues tracker.
> So, I spent a significant time replacing my old 1-line ocamlbuild
> command by a real Makefile (also because of a strange and probably
> unrelated linking bug which I still don't fully understand). I believe
> that an updated compiling howto is really needed, as well as a list of
> the main deleted features with respect to the last release, allowing
> users to estimate how much change their code will need.
>
I still use ocamlbuild with the old myocamlbuild.ml to compile my projects.
<*>: pkg_batteries, thread
is the main line in my _tags file I need.
Would it help to use a wiki to keep track of these things? All my code
is already adapted to the new system, so I don't find regressions
anymore to record.
> Other than that, I have not found any regression or other problems in
> this new release of the library, and I'm looking forward to see its
> further development.
>
> Tiphaine
>
I'm happy to push this forward, and there's a lot of good to add.
Patches welcome.
E.
prev parent reply other threads:[~2010-01-22 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 15:34 Edgar Friendly
2010-01-17 16:13 ` [Caml-list] " Dario Teixeira
2010-01-17 16:49 ` Stefano Zacchiroli
2010-01-17 20:12 ` Edgar Friendly
2010-01-17 20:08 ` Edgar Friendly
2010-01-19 11:06 ` Nicolas Cannasse
2010-01-19 12:41 ` Stefano Zacchiroli
2010-01-22 8:40 ` Tiphaine Turpin
2010-01-22 23:13 ` Edgar Friendly [this message]
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=4B5A3112.4020100@gmail.com \
--to=thelema314@gmail.com \
--cc=Tiphaine.Turpin@irisa.fr \
--cc=caml-list@yquem.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