From: Chris Hecker <checker@d6.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] monomorphic restriction or typing/scanf bug?
Date: Tue, 15 Oct 2002 14:20:11 -0700 [thread overview]
Message-ID: <4.3.2.7.2.20021015141908.03520b78@mail.d6.com> (raw)
In-Reply-To: <4.3.2.7.2.20021015135925.033299e8@mail.d6.com>
>Excellent, that's a fine workaround for my case!
Actually, I just realized that I didn't need the explicit type declaration
on there at all. Hmm, I could have sword there was some case like this
where I needed it with printf et al. Oh well.
Chris
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-10-15 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 3:29 Chris Hecker
2002-10-15 3:51 ` Jacques Garrigue
2002-10-15 12:19 ` Pierre Weis
2002-10-15 21:03 ` Chris Hecker
2002-10-15 21:20 ` Chris Hecker [this message]
[not found] ` <Pine.LNX.4.44.0210151424320.453-100000@grace.speakeasy.net >
2002-10-16 1:53 ` Chris Hecker
2002-10-16 6:42 ` [Caml-list] Local open (was: monomorphic restriction or typing/scanf bug?) Alain Frisch
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=4.3.2.7.2.20021015141908.03520b78@mail.d6.com \
--to=checker@d6.com \
--cc=caml-list@inria.fr \
/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).