From: John Carr <jfc@MIT.EDU>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Missing tabs
Date: Mon, 27 Oct 2003 08:12:34 -0500 [thread overview]
Message-ID: <200310271312.h9RDCYC1005087@no-knife.mit.edu> (raw)
In-Reply-To: Your message of "Sun, 26 Oct 2003 15:28:08 GMT." <20031026152808.GA8280@redhat.com>
> I've now read: http://caml.inria.fr/FAQ/FAQ_EXPERT-eng.html#printf
> thanks.
>
> Hmmm ... This does appear to violate the principle of least surprise.
I agree with this statement and the proposed less confusing
meaning of printf.
-------------------
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:[~2003-10-27 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 11:59 Richard Jones
2003-10-26 12:17 ` Nicolas George
2003-10-26 15:28 ` Richard Jones
2003-10-27 13:12 ` John Carr [this message]
2003-10-26 12:33 ` Remi Vanicat
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=200310271312.h9RDCYC1005087@no-knife.mit.edu \
--to=jfc@mit.edu \
--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).