From: John Prevost <prevost@maya.com>
To: caml-list@inria.fr
Subject: Re: another approach to sprintf (Re: ocaml 2.02 bug: curried printf)
Date: 24 Mar 1999 14:37:53 -0500 [thread overview]
Message-ID: <ya2pv5ywuem.fsf@zarya.maya.com> (raw)
In-Reply-To: Xavier Leroy's message of "Tue, 23 Mar 1999 17:17:53 +0100"
Xavier Leroy <Xavier.Leroy@inria.fr> writes:
> It's a cute trick. One drawback is that the format is not a character
> string, but needs to be expressed using special functions and infix
> operators. On the other hand, it doesn't need the special
> typechecking rules for format strings that we have in OCaml.
>
> With this special typechecking rules, I don't think Danvy's "partially
> evaluated" printf is any safer than OCaml's "interpreted" printf.
>
> Also, it doesn't solve (nor makes any worse) the issues with partial
> application of printf and friends that we discussed before.
It does, however, mean that people can extend the set of patterns that
can be used in printf in a more palatable way than the %a mechanism.
Especially with neat things like Danvy's "lis" combinator.
It also allows me to take two formats and concatenate them, like this:
let foo = int $ lit " " $ int $ string
let bar = lis int $ lit "!"
let zum = foo $ bar
which you can't do with O'Caml's format strings. (I tried to hack
something to do this once, using Obj.magic as the Printf module does.
I wasn't able to come up with anything, but I may be able to now that
I've had more experience looking at things like Danvy's printf.)
John.
next prev parent reply other threads:[~1999-03-25 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-06 1:38 ocaml 2.02 bug: curried printf William Chesters
1999-03-12 15:00 ` Xavier Leroy
1999-03-12 15:31 ` William Chesters
1999-03-19 8:47 ` another approach to sprintf (Re: ocaml 2.02 bug: curried printf) Eijiro Sumii
1999-03-23 16:17 ` Xavier Leroy
1999-03-24 19:37 ` John Prevost [this message]
1999-03-25 13:29 ` Christian Lindig
1999-03-25 20:52 ` John Prevost
1999-03-29 16:31 ` Xavier Leroy
1999-03-24 23:48 ` Frank A. Christoph
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=ya2pv5ywuem.fsf@zarya.maya.com \
--to=prevost@maya.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