caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Hendrik Tews <tews@cs.ru.nl>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] 3.09.3 release candidate 2
Date: Thu, 14 Sep 2006 09:48:30 +0200	[thread overview]
Message-ID: <wwuirjqq46p.fsf@tandem.cs.ru.nl> (raw)
In-Reply-To: <cd67f63a0609130917n1be2d2b8q1af978c9763687dc@mail.gmail.com> (Nicolas Pouillard's message of "Wed, 13 Sep 2006 18:17:56 +0200")


"Nicolas Pouillard" <nicolas.pouillard@gmail.com> writes:

   On 9/13/06, Hendrik Tews <tews@cs.ru.nl> wrote:
   >
   >    > I do not understand why you do need .cmo files when you have a library
   >    > (gramlib.cma or camlp4.cma) that includes these modules (note that .a
   >    > and .cmxa are also available for native linking).
   >
   > But with this line of reasoning, plexer.{o,cmx} should not be
   > installed either, shouln't it?

   Yes, but if I remember correctly it's you that request for these files
   to be installed?

Sure, but I didn't knew about the library, when I filed the bug
report. 

   So in order to be consistent either one do not expose at all the
   content of a library or one install all components (.cmo, .cmi, .cmx,
   .o). I tend to prefer the first one.

OK, Jacques clarified this, you need to install the .cmi .cmx
together with the library. .cmo and .o are in the library.

   > (I could still imagine some camlp4 application szenario, where
   > you need to use -linkall, but don't want to link all of
   > gramlib.cma. Then you would need the cmo itself, right? However,
   > this was not the case in my application.)

   Yes but it's a choice made by the library designer.

The library designer can hardly forsee all the possible usages of
the modules in his library. Therefore, in my opinion, one should
install all .cmi .cmo .cmx .o and have the libraries available
for convenience. The additional space needed is negligible (less
than 1M for both gramlib and plexer). Cases where users needed a
uncleaned ocaml source directory to compile certain features of
an application would then belong to the past.

Bye,

Hendrik


  parent reply	other threads:[~2006-09-14  7:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 11:21 3.09.3 release candidate 1 Damien Doligez
2006-08-30 12:18 ` [Caml-list] " Olivier Andrieu
2006-08-30 12:45   ` skaller
2006-08-30 13:06     ` Olivier Andrieu
2006-09-02  9:53 ` Jean-Marie Gaillourdet
2006-09-04 11:42   ` Damien Doligez
2006-09-08 14:47 ` 3.09.3 release candidate 2 Damien Doligez
2006-09-13  2:48   ` [Caml-list] " Aleksey Nogin
2006-09-13 13:30   ` Hendrik Tews
2006-09-13 15:05     ` Nicolas Pouillard
2006-09-13 15:32       ` skaller
2006-09-13 15:55         ` Hendrik Tews
2006-09-13 16:17           ` Nicolas Pouillard
2006-09-13 16:47             ` Chris King
2006-09-14  0:05               ` [Caml-list] " Jacques Garrigue
2006-09-14  7:48             ` Hendrik Tews [this message]
2006-09-13 16:35           ` [Caml-list] " skaller

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=wwuirjqq46p.fsf@tandem.cs.ru.nl \
    --to=tews@cs.ru.nl \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).