From: Malcolm Matalka <mmatalka@gmail.com>
To: Yaron Minsky <yminsky@janestreet.com>
Cc: Berke Durak <berke.durak@gmail.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml 4.02.0+dev4-2014-04-03 toplevel: module aliases no longer print module signature
Date: Sun, 27 Apr 2014 14:04:50 +0000 [thread overview]
Message-ID: <871twi98cd.fsf@gmail.com> (raw)
In-Reply-To: <CACLX4jQyr1U27eEooViKS8BCov7fJgcOt6JR_orMUp0+HN6_uA@mail.gmail.com> (Yaron Minsky's message of "Sun, 27 Apr 2014 09:18:26 -0400")
I make use of this trick often instead of going to documentation, it's
pretty convenient.
Yaron Minsky <yminsky@janestreet.com> writes:
> Sends preferable behavior to me, since it avoid overly long signatures and
> more clearly reflects the new semantics of module aliases.
>
> But it might be nice to have a way to see the contents of a module in the
> toplevel. Maybe steak the #typeof declaration from utop?
>
> y
> On Apr 27, 2014 8:47 AM, "Berke Durak" <berke.durak@gmail.com> wrote:
>
>> What happened?
>>
>> OCaml version 4.02.0+dev4-2014-04-03
>>
>> # module S = String;;
>> module S = String
>>
>> --
>> Berke Durak
>>
>> --
>> Caml-list mailing list. Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
next prev parent reply other threads:[~2014-04-27 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 12:52 Berke Durak
2014-04-27 13:18 ` Yaron Minsky
2014-04-27 13:45 ` Berke Durak
2014-04-27 13:58 ` ygrek
2014-04-27 14:19 ` Berke Durak
2014-04-27 14:21 ` Daniel Bünzli
2014-04-27 14:59 ` Berke Durak
2014-04-27 14:34 ` Leo White
2014-04-27 15:02 ` Berke Durak
2014-04-27 14:04 ` Malcolm Matalka [this message]
2014-05-03 20:18 ` Richard W.M. Jones
2014-05-03 20:21 ` Anil Madhavapeddy
2014-05-03 22:00 ` Richard W.M. Jones
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=871twi98cd.fsf@gmail.com \
--to=mmatalka@gmail.com \
--cc=berke.durak@gmail.com \
--cc=caml-list@inria.fr \
--cc=yminsky@janestreet.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).