Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: David Allsopp <dra-news@metastack.com>
To: OCaML List Mailing <caml-list@inria.fr>
Subject: RE: [Caml-list] ocaml considered dangerous
Date: Sat, 18 Jan 2014 09:43:44 +0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9E02E1B15@Remus.metastack.local> (raw)
In-Reply-To: <CAPFanBGg_a2FYgEi0aFEZOaOu_BuyZPYTHR1=rBzX_k+Dm0r2A@mail.gmail.com>

Gabriel Scherer wrote:
> David Allsopp wrote:
> > Does this new version fix positional specifiers?
> No, it does not. It makes the printf codebase easier to work with (if you
> know your GADTs),

Shame - it's an absence I find regularly irritating!

	Printf.printf "long-perfectly-readable-multi-line-format-string" id id id id date id id date date id :o)

> but lately the tendency has rather been to hope for *less* complex stuff in formats, rather than more.

Well, for me, the hope was that things that were supposed to have been there (in the docs) might be fixed! The comments closing PRs 3992, 4204, 4290 and 4321 all suggested that a rewrite would hope reintroduce positional specifiers. From the printf perspective, I thought the objective was to match all the implementable parts of ISO C's printf (i.e. skipping only the things which are not type-safe).


David 

  reply	other threads:[~2014-01-18  9:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 23:00 Jürgen Pfitzenmaier
2014-01-16 23:27 ` Milan Stanojević
2014-01-16 23:33 ` Daniel Bünzli
2014-01-17  0:43 ` Nicolas Braud-Santoni
2014-01-20 10:07   ` Goswin von Brederlow
2014-01-17  2:12 ` Jeff Meister
2014-01-17  2:38 ` Jacques Garrigue
2014-01-17  9:01   ` Gabriel Scherer
2014-01-18  0:39   ` Jon Harrop
2014-01-18  2:22     ` Jeremy Yallop
2014-01-18  7:04       ` Gabriel Scherer
2014-01-18  9:11         ` David Allsopp
2014-01-18  9:28           ` Gabriel Scherer
2014-01-18  9:43             ` David Allsopp [this message]
2014-01-18  9:59               ` Gabriel Scherer
2014-01-19  6:09         ` oleg

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=E51C5B015DBD1348A1D85763337FB6D9E02E1B15@Remus.metastack.local \
    --to=dra-news@metastack.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