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] naming conflicts (was: camlimages vs. labltk)
Date: Tue, 01 Apr 2003 11:51:05 -0800	[thread overview]
Message-ID: <4.3.2.7.2.20030401114643.01cdd9d8@localhost> (raw)
In-Reply-To: <45804206-644C-11D7-9F5C-0003930FCE12@inria.fr>


>First example:
>Second example (somewhat artificial):

Right, both of those jibe with what I thought you were saying.  I don't 
know enough to understand your functor solution, but -pack could also be 
used to solve both of these problems, if it did a real partial-link.  In 
other words, if I -pack B and A, and B uses a module A, then B's imports 
should be resolved to the A that it got packed with.  I don't know if this 
is simpler or more complex than your functor solution, but this one at 
least could still be handled by current partial linking tools (which is 
what -pack uses right now).  In fact, this might already happen with pack, 
since you can -pack modules that refer to other modules, and since they're 
now in a super-module, the semantics are that they should still refer to 
the submodules at the same scope.  So, this should already work with -pack, 
no?  If so, then the cmo/cma partial linking thing is the only thing wrong 
with -pack from both a package and namespace manager perspective.

Or am I missing something obvious?

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-04-01 19:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 19:33 [Caml-list] camlimages vs. labltk 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 [this message]
2003-04-08 10:33                               ` Damien Doligez
2003-03-31  1:21                         ` [Caml-list] camlimages vs. labltk Chris Hecker
2003-03-30  9:26                     ` 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.20030401114643.01cdd9d8@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