caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "François Bobot" <francois.bobot@cea.fr>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] META file standards for ppx extensions
Date: Fri, 10 Apr 2015 18:33:35 +0200	[thread overview]
Message-ID: <5527FB5F.2030203@cea.fr> (raw)
In-Reply-To: <017E69CBC52B4A698E545976E4CC24F4@erratique.ch>

On 10/04/2015 13:55, Daniel Bünzli wrote:
> Le vendredi, 10 avril 2015 à 13:04, François Bobot a écrit :
>> On 10/04/2015 11:42, Daniel Bünzli wrote:
>>> It's all about having a *composable* toolchain vs. inflexible monolithic black boxes.
>>
>> In order to gain flexibility, do you tried to link with findlib?
>
> If you are refering to this
>
> https://github.com/whitequark/ocaml-findlib/blob/master/src/findlib/findlib.mli
>
> then it doesn't seem to be much different from `ocamlfind query`, which as I already mentioned I
> had hard time to use to achieve my goals. But then maybe I should simply short-circuit all the
> ocamlfind flags logic and simply query the objects in the META files (which I didn't understand
> at the time could be done by simply using  "(%property)" notation; I used to fight with the
> various other % formatters).

findlib.mli doesn't implement the various % formatters. And it gives a much easier way to access the 
properties than to parse the output of ocamlfind.

You can look at the implementation of the frontend for how to use the library (ex: to use 
Fl_split.in_words) :
https://github.com/whitequark/ocaml-findlib/blob/master/src/findlib/frontend.ml

Regards,

-- 
François

  reply	other threads:[~2015-04-10 16:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 18:20 Dario Teixeira
2015-04-08 18:59 ` Drup
2015-04-08 19:59   ` Dario Teixeira
2015-04-08 20:37     ` Daniel Bünzli
2015-04-09 10:07       ` Dario Teixeira
2015-04-09 10:56     ` Gerd Stolpmann
2015-04-09 12:24       ` Dario Teixeira
2015-04-09 15:33         ` Daniel Bünzli
2015-04-09 16:45           ` Gerd Stolpmann
2015-04-09 17:27             ` Daniel Bünzli
2015-04-09 18:05               ` Daniel Bünzli
2015-04-09 22:26                 ` Gerd Stolpmann
2015-04-09 22:21               ` Gerd Stolpmann
2015-04-09 23:06                 ` Daniel Bünzli
2015-04-10  8:53                   ` François Bobot
2015-04-10  9:42                     ` Daniel Bünzli
2015-04-10 10:09                       ` Alain Frisch
2015-04-10 11:45                         ` Thomas Gazagnaire
2015-04-10 11:04                       ` François Bobot
2015-04-10 11:55                         ` Daniel Bünzli
2015-04-10 16:33                           ` François Bobot [this message]
2015-04-10 17:43                             ` Daniel Bünzli
2015-04-12  6:00                       ` Anil Madhavapeddy
2015-04-10 11:25                   ` Gerd Stolpmann
2015-04-10 11:55                     ` Daniel Bünzli
2015-04-09 15:45         ` Thomas Gazagnaire
2015-04-09 16:28           ` Dario Teixeira
2015-04-09 16:51             ` Gerd Stolpmann
2015-04-10 12:23         ` Daniel Bünzli
2015-04-10 14:55           ` Gerd Stolpmann

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=5527FB5F.2030203@cea.fr \
    --to=francois.bobot@cea.fr \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    /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).