From: Oleg <oleg@okmij.org>
To: kakadu.hafanana@gmail.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] type-safe printf
Date: Wed, 14 Sep 2016 20:19:23 +0900 [thread overview]
Message-ID: <20160914111923.GA3996@Magus.localnet> (raw)
In-Reply-To: <CAGmVoG1naW+w5WL=5VV5aBHrHphy-Bze6vZ_J15-vED_NBwfLg@mail.gmail.com>
> Functional unparsing by Olivier Danvy can be related article.
> http://www.brics.dk/RS/98/12/BRICS-RS-98-12.pdf
Well, in that vein one can point out
Functional un|unparsing
http://okmij.org/ftp/typed-formatting/index.html#derivation
which deals with both type-safe printf and scanf (and, moreover, using
exactly the same format for both printing and parsing) and derives even
more type-safe parsing/unparsing methods.
next prev parent reply other threads:[~2016-09-14 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 15:12 Андрей Бергман
2016-09-13 15:25 ` Mario Pereira
2016-09-13 15:36 ` Maxime Dénès
2016-09-13 15:31 ` Kakadu
2016-09-13 15:40 ` Daniel Bünzli
2016-09-14 11:19 ` Oleg [this message]
2016-09-13 15:38 ` David Allsopp
2016-09-13 17:54 ` Андрей Бергман
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=20160914111923.GA3996@Magus.localnet \
--to=oleg@okmij.org \
--cc=caml-list@inria.fr \
--cc=kakadu.hafanana@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;
as well as URLs for NNTP newsgroup(s).