From: Markus Mottl <mottl@miss.wu-wien.ac.at>
To: David Chemouil <David.Chemouil@enseeiht.fr>
Cc: caml-list@inria.fr
Subject: Re: convenient features
Date: Wed, 28 Jun 2000 19:29:16 +0200 [thread overview]
Message-ID: <20000628192916.B18617@miss.wu-wien.ac.at> (raw)
In-Reply-To: <3959C916.D1A3BDFD@enseeiht.fr>; from David.Chemouil@enseeiht.fr on Wed, Jun 28, 2000 at 11:44:54 +0200
On Wed, 28 Jun 2000, David Chemouil wrote:
> 1. One thing that really bothers me is the obligation to put object
> files in the good order, when linking them.
To my knowledge the reason for this is that you might otherwise have
difficulties with linking, because some library may contain a module
with the same name. By requiring correct order of files during linking,
it is possible to "override" the names provided in libraries or earlier
on the command line. E.g., if you want to use a different implementation
for sets, just link against some other set.cmo: it overrides whatever
was used before.
> As it is possible to
> generate the dependency graph (ocamldot does it), wouldn't it be
> possible for the linker to "flatten" it, in order for it to find alone
> the good order?
Maybe a tool that prints out a correct order for a set of files would
be helpful. This should be fairly easy to do - possibly just grab the
code from ocamldot.
Best regards,
Markus Mottl
--
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl
next prev parent reply other threads:[~2000-06-29 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 9:44 David Chemouil
2000-06-28 17:09 ` David Brown
2000-06-28 17:29 ` Markus Mottl [this message]
2000-06-29 16:57 ` Pierre Weis
2000-06-30 9:22 ` Christophe Raffalli
2000-06-30 18:10 ` Jean-Christophe Filliatre
2000-06-29 8:55 ` David Mentré
2000-06-29 9:19 ` Daniel de Rauglaudre
2000-06-30 0:42 ` Max 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=20000628192916.B18617@miss.wu-wien.ac.at \
--to=mottl@miss.wu-wien.ac.at \
--cc=David.Chemouil@enseeiht.fr \
--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