From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "ls-ocaml-developer-2006@m-e-leypold.de"
<ls-ocaml-developer-2006@m-e-leypold.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Custom operators in the revised syntax
Date: Sun, 13 May 2007 22:08:01 +0200 [thread overview]
Message-ID: <cd67f63a0705131308r4d2e189gff75bf252f6f32e9@mail.gmail.com> (raw)
In-Reply-To: <pa7irczp42.fsf@hod.lan.m-e-leypold.de>
On 5/13/07, ls-ocaml-developer-2006@m-e-leypold.de
<ls-ocaml-developer-2006@m-e-leypold.de> wrote:
>
> Arnaud Spiwack <aspiwack@lix.polytechnique.fr> writes:
>
> > About that, Coq uses something that proved itself to be rather
> > usefull, though the problematic is a bit different. It's called
> > notation scopes. The idea is that infix operators are defined in a
> > specific scope. That you can either open locally using (here the scope
> > is open)%scopeName, or globally by using Open Scope scopeName. When a
> > scope is open, all the infix operators are interpreted as its
> > definition in that scope. There are also a few more technicalities to
> > make it even more fun (for instance, you can bind a scope to a type t,
> > then, whenever an expression is inferred to be type t, the scope t is
> > automatically opened, it's a very useful feature).
> >
> > This allows a milde, but rather usable notation overloading.
> >
> > I've been wondering for quite a while if such a policy would be
> > reasonable/usefull for OCaml.
>
> I'd like to have a way to open moduls in a restricted scop, like
This is what the simple openin extension does (emulates using camlp4).
http://alain.frisch.fr/soft#openin
--
Nicolas Pouillard
next prev parent reply other threads:[~2007-05-13 20:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 20:55 Nicolas Pouillard
2007-05-10 21:35 ` [Caml-list] " Loup Vaillant
2007-05-10 22:25 ` Nicolas Pouillard
2007-05-11 6:52 ` Stefano Zacchiroli
2007-05-11 13:14 ` dmitry grebeniuk
2007-05-11 14:15 ` Loup Vaillant
2007-05-11 14:37 ` Jon Harrop
2007-05-11 14:46 ` Nicolas Pouillard
2007-05-12 2:48 ` Jon Harrop
2007-05-12 4:40 ` skaller
2007-05-12 4:47 ` Jon Harrop
2007-05-12 5:45 ` skaller
2007-05-12 5:59 ` Jon Harrop
2007-05-12 6:43 ` skaller
2007-05-12 10:22 ` Richard Jones
2007-05-13 15:42 ` Arnaud Spiwack
2007-05-13 16:04 ` ls-ocaml-developer-2006
2007-05-13 20:08 ` Nicolas Pouillard [this message]
2007-05-12 9:49 ` Nicolas Pouillard
2007-05-12 10:09 ` Jon Harrop
2007-05-11 14:52 ` Loup Vaillant
2007-05-11 18:32 ` skaller
2007-05-12 4:48 ` Jon Harrop
2007-05-11 18:23 ` skaller
2007-05-11 14:40 ` Nicolas Pouillard
2007-05-11 18:22 ` skaller
2007-05-11 14:36 ` Nicolas Pouillard
2007-05-11 14:47 ` brogoff
2007-05-11 14:51 ` Nicolas Pouillard
2007-05-11 18:25 ` brogoff
2007-05-11 20:37 ` Nicolas Pouillard
2007-05-12 22:54 ` Nicolas Pouillard
2007-05-13 0:27 ` ketti
2007-05-13 1:05 ` Christian Stork
2007-05-13 10:50 ` Nicolas Pouillard
2007-05-13 5:52 ` brogoff
2007-05-13 7:36 ` skaller
2007-05-13 13:12 ` Jacques Carette
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=cd67f63a0705131308r4d2e189gff75bf252f6f32e9@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=ls-ocaml-developer-2006@m-e-leypold.de \
/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).