From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: David Allsopp <dra-news@metastack.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Warnings opening modules (was: why is building ocaml hard?)
Date: Wed, 13 Jul 2016 14:20:02 +0200 [thread overview]
Message-ID: <1468412402.25014.109.camel@e130.lan.sumadev.de> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9011EA042A5@Remus.metastack.local>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
Am Mittwoch, den 13.07.2016, 12:08 +0000 schrieb David Allsopp:
> > I think that we need a syntax for toplevel module paths (e.g. I suggested
> > "open ^MyOwnProjectModule", resembling anchored regular expressions).
>
> Indeed, but rather than adding yet another piece of syntax, does it cause so much pain to move in the direction of just making the open declaration always require a toplevel module path?
I'm suggesting that mainly because it makes the transition easier - the
old and the new conventions could be used in parallel. Also, I don't
know whether there are actually reasonable applications of relative
module paths. It would be good to hear from other users about that.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-13 12:20 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 [this message]
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
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=1468412402.25014.109.camel@e130.lan.sumadev.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.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).