Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: David Sheets <sheets@alum.mit.edu>
To: Jeremy Yallop <yallop@gmail.com>
Cc: Malcolm Matalka <mmatalka@gmail.com>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] #show giving funny types
Date: Mon, 11 May 2015 12:10:54 +0100	[thread overview]
Message-ID: <CAAWM5TwuaPosit=r7wxOubjNB67jtKKp10uZto+6q-zZwg+n7A@mail.gmail.com> (raw)
In-Reply-To: <CAAxsn=HR0=cHFZkejmC26GNy1E+Q0Q-tyz1PC=qdfsEx7saNYA@mail.gmail.com>

On Fri, May 8, 2015 at 12:13 PM, Jeremy Yallop <yallop@gmail.com> wrote:
> On 7 May 2015 at 20:19, Malcolm Matalka <mmatalka@gmail.com> wrote:
>> I'm poking around in the toplevel and noticed that some types are coming
>> out funny.  In particular 'int' is being shown as
>> 'UnixLabels.file_perm'.
>>
>> For example doing "#show Async_unix.Reader;;" in utop gives me an output
>> with:
>>
>>     val really_read :
>>       t ->
>>       ?pos:UnixLabels.file_perm ->
>>       ?len:UnixLabels.file_perm -> Arg.usage_msg -> [ `Eof of
>>       UnixLabels.file_perm | `Ok ] Async_kernel.Deferred.t
>>
>> I'm not sure if I've missed this in the list, but is anyone else
>> experiencing this?

I believe this was PR 6763 <http://caml.inria.fr/mantis/view.php?id=6763>.

> This looks like a problem with the -short-paths option.  Could you
> open a Mantis ticket?
>
> --
> 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

      reply	other threads:[~2015-05-11 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 19:19 Malcolm Matalka
2015-05-08 11:13 ` Jeremy Yallop
2015-05-11 11:10   ` David Sheets [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='CAAWM5TwuaPosit=r7wxOubjNB67jtKKp10uZto+6q-zZwg+n7A@mail.gmail.com' \
    --to=sheets@alum.mit.edu \
    --cc=caml-list@inria.fr \
    --cc=mmatalka@gmail.com \
    --cc=yallop@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