caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Brown <caml-list@davidb.org>
To: caml-list@inria.fr
Subject: RE: Undefined labels
Date: Thu, 18 Nov 1999 12:08:32 -0800 (PST)	[thread overview]
Message-ID: <14388.23744.409028.106149@opus.davidb.org> (raw)
In-Reply-To: <199911171001.LAA26208@yana.inria.fr>

Gerard Huet writes:
 > open is a facility that is convenient to the programmer because the code is
 > uncluttered with long explicit names, but it is of course a source of bugs.
 > The addition of a new binding in a module may change drastically the
 > semantics of modules which open it, in a way that stays unnoticed if types
 > match. 

One feature I like of Python and Erlang is a selective import.  It is
possible to specify only the items that you would like imported from a
module.  If you use the selective open, the open declaration itself
states which symbols come from that module.  Since the scope is
explicit, it makes it easy to tell where something is coming from.

I'm not familiar with the parser too much, but perhaps something like:

open (bleep, bloop, SubMod) Module;;

There probably should also be a way to open all of the constructors of
a type.

Dave Brown




  reply	other threads:[~1999-11-19 13:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-12 17:06 Manuel Fahndrich
1999-11-16  0:30 ` Brian Rogoff
1999-11-19 14:35   ` Anton Moscal
1999-11-17  9:54 ` Gerard Huet
1999-11-18 20:08   ` David Brown [this message]
1999-11-19 16:18     ` Markus Mottl
1999-11-20 23:49       ` Packages? skaller
  -- strict thread matches above, loose matches on Subject: below --
1999-10-14  0:58 Announcement: automatically resizing arrays Markus Mottl
1999-11-11 11:39 ` Undefined labels skaller
1999-11-12  9:28   ` Jean-Christophe Filliatre
1999-11-12 23:01     ` skaller
1999-11-12  9:54   ` William Chesters
1999-11-12 12:47   ` Christian RINDERKNECHT
1999-11-12 17:11     ` Jean-Francois Monin

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=14388.23744.409028.106149@opus.davidb.org \
    --to=caml-list@davidb.org \
    --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).