Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Chris Hecker <checker@d6.com>
To: Damien Doligez <Damien.Doligez@inria.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] camlimages vs. labltk
Date: Sun, 30 Mar 2003 17:21:01 -0800	[thread overview]
Message-ID: <4.3.2.7.2.20030330171713.046f75b8@localhost> (raw)
In-Reply-To: <45905683-6297-11D7-B6B4-0003930FCE12@inria.fr>


>How do you make sure that two different libraries never use the same
>namespace ?  And if I need to use two versions of the same library
>in my program, how do you make sure that two versions of the same
>library never use the same namespace ?

Are you saying because they cross reference each other, or because they are 
the same name?  If -pack was changed to work in the way we've been talking 
about (basically, the submodules are in a cma not cmo), then the user of 
the libraries could just pack them in different outer names, no?  In other 
words, -pack would be able to be used as a namespace renamer, or as a 
library packer, etc., but it has the advantage of being a single solution 
as opposed to having a namespace and a pack syntax/semantic.  If you've 
got  cross referencing, say A uses B version 1 and you want to use B 
version 2, then you pack A and Bv1 into a single ABv1 library, and you use 
B and it should "just work".

Assuming it's not impossible to make -pack work this way (not forcing link 
of all submodules), it seems better to have a single solution as opposed to 
multiple.  Unless I'm missing something?

Chris

-------------------
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


  parent reply	other threads:[~2003-03-31  1:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 19:33 Shivkumar Chandrasekaran
2003-03-26  8:25 ` Alessandro Baretta
2003-03-26  8:33   ` Sven Luther
2003-03-26  9:00     ` Alessandro Baretta
2003-03-26 10:50       ` Sven Luther
2003-03-26 11:24         ` Alessandro Baretta
2003-03-26 11:38           ` Sven Luther
2003-03-26 19:08             ` Chris Hecker
2003-03-26 21:08               ` Alessandro Baretta
2003-03-27 17:23                 ` David Brown
2003-03-27 19:46                 ` Chris Hecker
2003-03-28  5:33                   ` Alessandro Baretta
2003-03-28  5:35                     ` David Brown
2003-03-28 14:10                   ` Damien Doligez
2003-03-28 15:00                     ` Sven Luther
2003-03-30 10:06                       ` Damien Doligez
2003-03-30 10:38                         ` Sven Luther
2003-04-01 14:14                           ` [Caml-list] naming conflicts (was: camlimages vs. labltk) Damien Doligez
2003-04-01 15:05                             ` Benjamin C. Pierce
2003-04-01 19:51                             ` Chris Hecker
2003-04-08 10:33                               ` Damien Doligez
2003-03-31  1:21                         ` Chris Hecker [this message]
2003-03-30  9:26                     ` [Caml-list] camlimages vs. labltk Alessandro Baretta
2003-03-26 18:49     ` Shivkumar Chandrasekaran
2003-03-26 10:48   ` Stefano Zacchiroli
2003-03-26 10:55     ` Sven Luther
2003-03-26 14:10       ` Stefano Zacchiroli

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=4.3.2.7.2.20030330171713.046f75b8@localhost \
    --to=checker@d6.com \
    --cc=Damien.Doligez@inria.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