From: Jean-Christophe Filliatre <Jean-Christophe.Filliatre@lri.fr>
To: Lukasz Lew <ll189417@zodiac.mimuw.edu.pl>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Feature request.
Date: Wed, 9 Apr 2003 08:32:35 +0200 [thread overview]
Message-ID: <16019.48771.767140.795030@gargle.gargle.HOWL> (raw)
In-Reply-To: <Pine.LNX.4.44.0304081318010.16256-100000@zodiac.mimuw.edu.pl>
Lukasz Lew writes:
>
> 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?
>
> Why some constructions are restricted to global (module) use?
Be aware that it may easily lead to scope issues.
In SML, there used to be local exceptions (exception E in ...) and it
was breaking type soundness, since an exception could obviously escape
the scope of its declaration (unless the compiler is doing a static
analysis over exceptions possibly raised, difficult yet feasible, but
SML was not).
I guess that with a "type ... in" construct, a type could probably
escape its scope the same way, leading to serious issues in assigning
legal types to expressions.
Just a guess...
--
Jean-Christophe Filliâtre (http://www.lri.fr/~filliatr)
-------------------
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
next prev parent reply other threads:[~2003-04-09 6:37 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
2003-04-09 6:32 ` Jean-Christophe Filliatre [this message]
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=16019.48771.767140.795030@gargle.gargle.HOWL \
--to=jean-christophe.filliatre@lri.fr \
--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