From: Alain Frisch <alain.frisch@lexifi.com>
To: Yotam Barnoy <yotambarnoy@gmail.com>,
Hendrik Boom <hendrik@topoi.pooq.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Warnings opening modules (was: why is building ocaml hard?)
Date: Fri, 15 Jul 2016 20:50:25 +0200 [thread overview]
Message-ID: <0017d57b-7316-c5a8-87fc-db297d8fbb20@lexifi.com> (raw)
In-Reply-To: <CAN6ygO=cogFgUj9oADT6Cy-LEiZ7B=PYhpyufzcXEoawaYUhWg@mail.gmail.com>
On 15/07/2016 18:57, Yotam Barnoy wrote:
> The problem seems to stem from the fact that the same open statements
> which we use to import code (and which are available in every
> language) are also used as part of OCaml's super-flexible module
> system. This makes it hard to come up with easy, simple shortcuts for
> functionality available in other languages, because it needs to fit in
> the far more complex general module language.
There would really be no difficulty to allow specifying which components
to bring in scope in an "open" statement. One just need to decide if it
is a good idea from a language design point of view, and then agree on /
fight over a syntax. (One needs to distinguish of course between
various kinds of components.)
Alain
next prev parent reply other threads:[~2016-07-15 18:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 11:57 David Allsopp
2016-07-10 19:45 ` Gerd Stolpmann
2016-07-13 12:08 ` David Allsopp
2016-07-13 12:20 ` Gerd Stolpmann
2016-07-13 12:30 ` David Allsopp
2016-07-14 9:03 ` Goswin von Brederlow
2016-07-15 9:52 ` David Allsopp
2016-07-15 16:13 ` Hendrik Boom
2016-07-15 16:57 ` Yotam Barnoy
2016-07-15 18:09 ` Jeremy Yallop
2016-07-15 18:26 ` Hendrik Boom
2016-07-15 18:58 ` Yotam Barnoy
2016-07-15 19:26 ` Hezekiah M. Carty
2016-07-15 19:42 ` Yotam Barnoy
2016-07-15 19:52 ` Jeremy Yallop
2016-07-15 20:25 ` Yotam Barnoy
2016-07-15 18:50 ` Alain Frisch [this message]
2016-07-15 19:44 ` Hendrik Boom
2016-07-15 17:04 ` Gerd Stolpmann
2016-07-20 7:49 ` Louis Gesbert
2016-07-16 7:40 ` Petter A. Urkedal
2016-07-16 9:58 ` vrotaru.md
2016-07-19 16:37 ` Yotam Barnoy
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=0017d57b-7316-c5a8-87fc-db297d8fbb20@lexifi.com \
--to=alain.frisch@lexifi.com \
--cc=caml-list@inria.fr \
--cc=hendrik@topoi.pooq.com \
--cc=yotambarnoy@gmail.com \
/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).