From: Hendrik Tews <H.Tews@cs.ru.nl>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] positional specifiers in format strings
Date: Fri, 25 May 2007 09:36:35 +0200 [thread overview]
Message-ID: <wwu4pm11hj0.fsf@tandem.cs.ru.nl> (raw)
In-Reply-To: <000901c79e07$6d375150$6a7ba8c0@treble> (David Allsopp's message of "Thu, 24 May 2007 14:28:32 +0100")
"David Allsopp" <dra-news@metastack.com> writes:
> Objective Caml version 3.10.0
>
> # Printf.printf "%5$f";;
> Bad conversion %$, at char number 0 in format string ``%5$f''
> # Printf.printf "%.*3$f";;
> Bad conversion %3, at char number 0 in format string ``%.*3$f''
Positional specifiers aren't new and, sadly, neither's the bug -
http://caml.inria.fr/mantis/view.php?id=4204
That's another point where the txt and html documentations
diverge: positional specifiers are only in the 3.09 html
documentation, but not in the txt version. That's why they got
classified as new.
Hendrik
prev parent reply other threads:[~2007-05-25 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070524131457.916E9BC77@yquem.inria.fr>
2007-05-24 13:28 ` David Allsopp
2007-05-25 7:36 ` Hendrik Tews [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=wwu4pm11hj0.fsf@tandem.cs.ru.nl \
--to=h.tews@cs.ru.nl \
--cc=caml-list@yquem.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