caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: tim@fungible.com (Tim Freeman)
To: ll189417@zodiac.mimuw.edu.pl
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Feature request.
Date: Tue,  8 Apr 2003 11:03:49 -0700	[thread overview]
Message-ID: <20030408180702.DD2927F4D@lobus.fungible.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304081318010.16256-100000@zodiac.mimuw.edu.pl> (message from Lukasz Lew on Tue, 8 Apr 2003 13:31:32 +0200 (CEST))

From: Lukasz Lew <ll189417@zodiac.mimuw.edu.pl>
>  I found that it would be usefull if some of the language constructions 
>  could be made localy. For example "open ... in" or "type ... in".
>  Why "open in" isn't in standard parser?

I don't know.

>  Why some constructions are restricted to global (module) use?

You can do "let module ... in", so "global" is not equivalent to
"module".  I don't like open statements anyway because they require me
to read many of the opened modules to discover which module provides
the symbol.  I prefer to establish one-letter module names if I feel
the need for brevity, so "let module" is all I need.

-- 
Tim Freeman                                                  tim@fungible.com
Which is worse: ignorance or apathy? Who knows? Who cares?
GPG public key fingerprint ECDF 46F8 3B80 BB9E 575D  7180 76DF FE00 34B1 5C78 

-------------------
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-08 18:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 11:31 Lukasz Lew
2003-04-08 16:15 ` Alain.Frisch
2003-04-08 19:06   ` Lukasz Lew
2003-04-08 18:03 ` Tim Freeman [this message]
2003-04-09  6:32 ` Jean-Christophe Filliatre
2003-04-09  7:44   ` Alain.Frisch
2003-04-12 20:35   ` Andreas Rossberg

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=20030408180702.DD2927F4D@lobus.fungible.com \
    --to=tim@fungible.com \
    --cc=caml-list@inria.fr \
    --cc=ll189417@zodiac.mimuw.edu.pl \
    /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).