From: Edgar Friendly <thelema314@gmail.com>
To: Roland Zumkeller <roland.zumkeller@gmail.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Explicitly referring to top-level definitions
Date: Sun, 08 Mar 2009 10:45:32 -0500 [thread overview]
Message-ID: <49B3E81C.60404@gmail.com> (raw)
In-Reply-To: <d02dcb040903071210x5f3cb7d6g7c8ab2742d58e911@mail.gmail.com>
Roland Zumkeller wrote:
> Hi,
>
> Is there a way to qualify identifiers explicitly so as to make them
> refer to top-level definitions?
>
> # type t = int;;
> type t = int
> # module A = struct type t = t end;;
> The type abbreviation t is cyclic
>
> Is it possible to write something like "type t = Top.t"?
>
> Best,
>
> Roland
In the case I've had to do this, I just created an alias for the
top-level definition. ex.
# type t = int;;
# type t_alias = t;;
# module A = struct type t = t_alias end;;
E
prev parent reply other threads:[~2009-03-08 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 20:10 Roland Zumkeller
2009-03-08 15:45 ` Edgar Friendly [this message]
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=49B3E81C.60404@gmail.com \
--to=thelema314@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=roland.zumkeller@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).