From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: Sven LUTHER <luther@dpt-info.u-strasbg.fr>,
Gerd Stolpmann <info@gerd-stolpmann.de>,
Alessandro Baretta <alex@baretta.com>, Ocaml <caml-list@inria.fr>
Subject: Re: We should start using -pack by default when building libraries, (was : Re: [Caml-list] Meta module in findlib and the need for namespaces)
Date: Tue, 24 Sep 2002 08:30:41 +0200 [thread overview]
Message-ID: <20020924063041.GA1436@iliana> (raw)
In-Reply-To: <20020923163619.A16997@pauillac.inria.fr>
On Mon, Sep 23, 2002 at 04:36:19PM +0200, Xavier Leroy wrote:
> > > Note that dynlink.cma not only contains Meta, but also other modules
> > > with plain names: Misc, Config, Ident, Path, Types, i.e. names for
> > > which name clashes are much more likely than for cryptic names.
> >
> > Well, is it not for exactly this kind of problems that the -pack option
> > was implemented ?
>
> Yes, exactly.
:)))
> For other existing libraries, backward compatibility can deter using
> -pack, but I'd encourage authors of new libraries to use it in order
> to export only one compilation unit.
Could we consider making using -pack the standard for a future version of
ocaml (3.07) and add a -nopack version for those that don't want to use
it, especially when building .cmas ?
This would need a bit of discussion first, but mostly, i don't think
anyone would object to this, at least not very strongly.
That said ...
John Carr <jfc@MIT.EDU> Wrote :
| OCaml 3.06 does not support -pack when using native code on a system
| without the GNU linker. If you release software that depends on -pack,
| I will not be able to use it.
Well, this would cause a problem, which need to be solved before -pack
is supported as standard. What are exactly the cases were it causes
problem, (AIX when not using the GNU linker, i guess, but also maybe
windows ?) and is there any chance this can be solved soonly ?
Alternatively, this could be a feature that could be enabled/disabled at
build time ?
Friendly,
Sven Luther
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-09-24 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 14:47 [Caml-list] Meta module in findlib and the need for namespaces Alessandro Baretta
2002-09-22 21:29 ` Gerd Stolpmann
2002-09-23 8:43 ` We should start using -pack by default when building libraries, (was : Re: [Caml-list] Meta module in findlib and the need for namespaces) Sven LUTHER
2002-09-23 14:36 ` Xavier Leroy
2002-09-24 6:30 ` Sven LUTHER [this message]
2002-09-25 4:48 ` [Caml-list] Re: We should start using -pack by default when building libraries, (was : " Michaël Grünewald
2002-09-25 9:32 ` Sven LUTHER
2002-09-25 19:33 ` Michaël Grünewald
2002-09-26 11:00 ` Sven
2002-09-29 5:27 ` Michaël Grünewald
2002-09-23 15:03 ` [Caml-list] Re: We should start using -pack by default when building libraries John Carr
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=20020924063041.GA1436@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=alex@baretta.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=xavier.leroy@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