caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: "Michaël Grünewald" <michael-grunewald@wanadoo.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: We should start using -pack by default when building libraries, (was : Re: Meta module in findlib and the need for namespaces)
Date: Wed, 25 Sep 2002 11:32:29 +0200	[thread overview]
Message-ID: <20020925093229.GA1424@iliana> (raw)
In-Reply-To: <87d6r2llnw.fsf@ketanu.dyndns.org>

On Wed, Sep 25, 2002 at 06:48:19AM +0200, Michaël Grünewald wrote:
> Sven LUTHER <luther@dpt-info.u-strasbg.fr> writes:
> 
> > 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.
> 
> So every unmaintained code and Makefiles becomes all suddenly obsoletes ?

unmaintained code is not good to have around anyway, it will most
probably break some in the future anyway (when there is a ocaml 4.0 for
example ?).

> This is a really bad thing to do things like this, and it is so easy to
> write wrappers scripts over the compiler, so it has defaults suitable for
> your needs ... There is no need to modify standards for that.

But the change is only adding the appropriate open at the top of the
files, i guess it could even be done with automatic translation or
something such.

Also, i guess the Pervasive library will be opened by default, and maybe
also the standard library.

This namespace problem is one that ocaml was having since a long time,
and which will become only worse as time passes and more library will be
written. So are you saying that we should stay with something that will
cause more and more problem as time passes, just because some obsolete
and unmaintained code will break in this case ? 

Anyway, this can be done in a painless incremental way.

We decide that starting now, all libraries should use the -pack option
when it is possible, and slowly migrate to using that for the existing
code, but still keep the default behavior as usual. Later, when we are
satisfied that it works well and most libraries are ported to using
-pack (and the acompanying code using it also), we can modify the
behavior to use -pack by default for libraries.

And btw, it is more natural to write, for example Gdk.Event.Button than
GdkEvent.Button, as we do now, don't you think ?

> > 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 ?
> 
> E.g. with the `-pack' option ? :)

At build time of the ocaml compiler suite, with a configure option, so
that you could build an ocaml suite to either use -pack by default or
not, and a ocamlc option to return the default used pack option, so you
could use it to write the libraries accordyingly (well, maybe this is
not easily).

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


  reply	other threads:[~2002-09-25 10:10 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
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 [this message]
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=20020925093229.GA1424@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --cc=michael-grunewald@wanadoo.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).