From: Eijiro Sumii <sumii@venus.is.s.u-tokyo.ac.jp>
To: caml-list@inria.fr
Subject: another approach to sprintf (Re: ocaml 2.02 bug: curried printf)
Date: Fri, 19 Mar 1999 17:47:20 +0900 [thread overview]
Message-ID: <19990319174720-10695P.sumii@harp.is.s.u-tokyo.ac.jp> (raw)
In-Reply-To: Your message of "Fri, 12 Mar 1999 16:00:17 +0100" <19990312160017.60444@pauillac.inria.fr>
Hello,
(Excuse me for changing the subject and providing no French
version...)
I don't know very much about *printf in ocaml, but how about Olivier
Danvy's approach to sprintf (http://www.brics.dk/RS/98/12/index.html)?
It seems safer and faster than ordinary "interpretive" approach. I'd
like to hear what do you (I mean, readers of this mailing list) think
about it.
> Subject: Re: ocaml 2.02 bug: curried printf
> From: Xavier Leroy <Xavier.Leroy@inria.fr>
> Date: Fri, 12 Mar 1999 16:00:17 +0100
...
> We can go back to the 2.01 implementation of sprintf, of course, but
> it's less efficient than the one based on extensible buffers, and also
> prevents interesting code sharing between sprintf and bprintf.
>
> The alternative is to keep a buffer-based sprintf that is efficient
> and consistent with printf ("consistent" in the sense of "as weird as"),
> but is not really usable in partial application contexts.
>
> Any opinions?
// Eijiro Sumii <sumii@yl.is.s.u-tokyo.ac.jp>
//
// Kobayashi Laboratory, Department of Information Science,
// Graduate School of Science, University of Tokyo
next prev parent reply other threads:[~1999-03-19 18:25 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 ` Eijiro Sumii [this message]
1999-03-23 16:17 ` another approach to sprintf (Re: ocaml 2.02 bug: curried printf) Xavier Leroy
1999-03-24 19:37 ` John Prevost
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=19990319174720-10695P.sumii@harp.is.s.u-tokyo.ac.jp \
--to=sumii@venus.is.s.u-tokyo.ac.jp \
--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