From: Thierry Bravier <Thierry.Bravier@dassault-aviation.fr>
To: Andrew Martin <amartin@ibmoto.com>, caml-list <caml-list@inria.fr>
Subject: Re: CamlIDL - stub code generator and COM binding for OCaml
Date: Fri, 12 Mar 1999 11:47:01 +0100 [thread overview]
Message-ID: <36E8F0A4.A7EE895@dassault-aviation.fr> (raw)
In-Reply-To: <36E56E68.3C58A858@ibmoto.com>
Andrew Martin wrote:
> How about the following change to the Ocaml language with two orthogonal
> extensions to the use of the "open" keyword:
>
> 1) allow open to be used locally (open M in (f a b c)) and
> 2) allow open t where t is a type expression as well as open M where M is a
> module expression (open t in expr)
Both extensions look really neat to me.
They should solve the common record label issue (as explained by A. Martin)
and also another seemingly unrelated problem:
(see Christophe Raffalli's last message)
how to use A.B.(+) in an infix way ?
With 'open in' you could write:
module F = struct let (+) = (+.) and (-) = (-.) and ( * ) = ( *. ) end
let delta a b c = open F in b*b - 4.0 *a*c
without 'open in' you would not be able to 'open F'
because it would hide useful Pervalises.(+) ... till the end of current struct
(most often current file).
Thanks.
--
Thierry Bravier Dassault Aviation - DGT / DPR / DESA
78, Quai Marcel Dassault F-92214 Saint-Cloud Cedex - France
Telephone : (33) 01 47 11 53 07 Telecopie : (33) 01 47 11 52 83
E-Mail : mailto:thierry.bravier@dassault-aviation.fr
next prev parent reply other threads:[~1999-03-12 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-05 10:41 Xavier Leroy
1999-03-05 20:46 ` Andrew Martin
1999-03-08 9:41 ` Sven LUTHER
1999-03-09 16:07 ` Xavier Leroy
1999-03-09 18:54 ` Andrew Martin
1999-03-12 10:47 ` Thierry Bravier [this message]
1999-03-10 9:11 ` Pierre Weis
1999-03-10 9:43 ` Jacques GARRIGUE
1999-03-09 21:57 ` doligez
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=36E8F0A4.A7EE895@dassault-aviation.fr \
--to=thierry.bravier@dassault-aviation.fr \
--cc=amartin@ibmoto.com \
--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