caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: brogoff@speakeasy.net
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Error during partial linking
Date: Tue, 22 Oct 2002 10:21:07 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0210221008100.6093-100000@grace.speakeasy.net> (raw)
In-Reply-To: <20021022190056.A28301@pauillac.inria.fr>

On Tue, 22 Oct 2002, Xavier Leroy wrote:
> Coming back to your initial desire to "pack" Baire (if I may say so),
> I would very strong advise Diego to name his "List" module something
> else, to avoid conflict with the standard library module of the same
> name.  The hypothesis that compilation units are identified by unique
> names is really essential to the way the OCaml compilers work.  I know
> it's sometimes an annoyance (all cool names are already taken by the
> standard lib :-), but you're really going to run into trouble with
> name conflicts.

This is one of those things that's always troubled me (perhaps there's another 
petty complaint coming up) about OCaml. In a language with a hierarchical 
module system, it seems that we should be able to avoid such problems by 
having the standard library packages nested under a "Std" module, or something 
like that, so that List, Array, etc., become Std.List, Std.Array, etc, as we 
do now for the labeled modules. 

I suppose it's too late now for such a change, but I'm pretty sympathetic to 
people who grouse over the fact that lots of good names are taken. 

-- Brian


-------------------
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:[~2002-10-22 17:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22  5:33 Yang Shouxun
2002-10-22  8:42 ` Xavier Leroy
2002-10-22  9:21   ` Sven Luther
2002-10-22 16:17     ` Chris Hecker
2002-10-22 16:47       ` Sven Luther
2002-10-22 17:14     ` [Caml-list] on the -pack option Xavier Leroy
2002-10-22 19:30       ` Sven Luther
2002-10-22  9:37   ` [Caml-list] Error during partial linking Yang Shouxun
2002-10-22 16:07     ` Chris Hecker
2002-10-22 17:00       ` Xavier Leroy
2002-10-22 17:12         ` Chris Hecker
2002-10-22 17:21         ` brogoff [this message]
2002-10-22 20:06           ` Dmitry Bely
2002-10-22 20:25             ` Alain Frisch
2002-10-22 20:37               ` Dmitry Bely
2002-10-22 20:53                 ` Alain Frisch
2002-10-22 21:10                   ` Dmitry Bely
2002-10-23  7:15                 ` Alessandro Baretta
     [not found]         ` <Pine.LNX.4.44.0210221008100.6093-100000@grace.speakeasy.ne t>
2002-10-22 17:44           ` Chris Hecker
2002-10-22 19:31         ` Sven Luther
2002-10-22 23:38           ` Chris Hecker
2002-10-23  4:16             ` David Brown
2002-10-23 10:01           ` Diego Olivier Fernandez Pons
2002-10-23 10:36             ` Sven Luther
2002-10-23 11:41               ` Alessandro Baretta

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=Pine.LNX.4.44.0210221008100.6093-100000@grace.speakeasy.net \
    --to=brogoff@speakeasy.net \
    --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;
as well as URLs for NNTP newsgroup(s).