Re: [Caml-list] Preferred layout for new packages

[Edgar Friendly <thelema314@gmail.com>]

On 11/14/2012 6:43 AM, Marek Kubica wrote:
> Hi,
>
> I'm kinda new to the OCaml eco system and therefore a bit confused on a
> number of issues:
>
> 1. Build system: what to use? I have tried OMake some time ago and
> liked the automatic recompilation, but writing the OMakefiles was quite
> awful and it does not seem popular. What is the state of the art
> solution?
The community is trying to standardize on Oasis, which generates 
ocamlbuild-based build systems.  In the future, this may generate some 
other build system if a better one comes out.
> 2. Unit tests: I used OUnit which was okay, but maybe there are better
> solutions? I've seen that there is Kaputt and I have seen that there is
> https://github.com/camlunity/ocaml-quickcheck as well as
> https://github.com/vincent-hugot/iTeML which was extracted from
> batteries recently.
iTeML is more of a test extraction framework, and builds on top of OUnit 
and a hacked version of the Jane St. quickcheck library.  It can easily 
support other frameworks, and it would be interesting to explore a 
custom framework designed with iTeML in mind.
> 3. Stdlib: I don't mind depending on batteries and/or core, are there
> any reasons against? Especially in the unit tests it drove me nuts that
> I wasn't able to display results without writing printers, and I know
> batteries has at least a generic printer.
Batteries' dump function is a terrible printer for anything beyond the 
most basic of purposes, just as the Pervasives.compare is also 
terrible.  Batteries' printer combinators (`List.print Int.print stdout 
[1;2;3]`) are what I use for most purposes.

E.