From: henri dubois-ferriere <henridf@gmail.com>
To: Jean-Christophe Filliatre <jean-christophe.filliatre@lri.fr>
Cc: Pierre Weis <pierre.weis@inria.fr>,
"Basile Starynkevitch [local]" <basile.starynkevitch@inria.fr>,
caml-list@inria.fr
Subject: Re: [Caml-list] kprintf with user formatters
Date: Fri, 16 Jul 2004 00:23:09 -0700 [thread overview]
Message-ID: <d61254fb040716002313ae6402@mail.gmail.com> (raw)
In-Reply-To: <16631.32784.526557.747099@gargle.gargle.HOWL>
this sounds interesting! could you point us to any available code
showing more of this in practice?
thanks
henri
On Fri, 16 Jul 2004 09:13:20 +0200, Jean-Christophe Filliatre
<jean-christophe.filliatre@lri.fr> wrote:
>
> Pierre Weis writes:
> >
> > If I understand properly:
> >
> > - you want to skip the runtime time penalty of formatting the
> > arguments to string before discarding the result,
> > - you even want not to parse the format string,
> > - ideally you also want NOT TO EVALUATE the reminding arguments of
> > your printf call ?
> >
> > Hmm, this sounds extremely lazy to me; so this suggests thunk
> > programming; hey, we have that in the language, so let's go!
> >
> > let log level thunk =
> > if may_log level then thunk ();;
> >
> > ...
> >
> > log 2 (fun () ->
> > eprintf "Argument 1 is hard to compute %d\n" (ackermann x x))
>
> I also use the same kind of trick in practice, with a little
> refinement to avoid building the closure. I introduce higher-order
> functions such as
>
> val if_debug : ('a -> unit) -> 'a -> unit
>
> which behaves like application when the debug flag is on (and does
> nothing otherwise). Then you can simply write
>
> ...
> if_debug eprintf "this is a message";
> ...
>
> I even introduce variants for functions with more than one argument to
> be able to write stuff like
>
> ...
> if_debug3 eprintf "syntax tree is %a@." print_tree t;
> ...
>
> without addition of parentheses. I still find this very convenient and
> not obtrusive as far as style is concerned.
>
> Hope this helps,
> --
> Jean-Christophe Filliâtre (http://www.lri.fr/~filliatr)
>
>
>
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
> Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-07-16 7:23 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 16:32 Damien
2004-07-14 21:10 ` Pierre Weis
2004-07-15 0:17 ` Markus Mottl
2004-07-15 7:30 ` David MENTRE
2004-07-15 7:59 ` Jean-Christophe Filliatre
2004-07-15 23:35 ` henri dubois-ferriere
2004-07-15 7:39 ` Damien
2004-07-15 12:19 ` Markus Mottl
2004-07-15 12:42 ` Basile Starynkevitch [local]
2004-07-15 13:45 ` Markus Mottl
2004-07-15 14:22 ` Basile Starynkevitch [local]
2004-07-15 14:57 ` Markus Mottl
2004-07-16 6:47 ` Pierre Weis
2004-07-16 7:13 ` Jean-Christophe Filliatre
2004-07-16 7:23 ` henri dubois-ferriere [this message]
2004-07-16 7:44 ` Jean-Christophe Filliatre
2004-07-16 17:56 ` Markus Mottl
2004-07-19 9:17 ` Pierre Weis
2004-07-19 9:32 ` Jean-Christophe Filliatre
2004-07-16 7:21 ` henri dubois-ferriere
2004-07-16 17:44 ` Markus Mottl
2004-07-19 10:10 ` Pierre Weis
2004-07-19 10:43 ` Jon Harrop
2004-07-21 15:52 ` Pierre Weis
2004-07-21 17:43 ` lazyness in ocaml (was : [Caml-list] kprintf with user formatters) Daniel Bünzli
2004-07-22 16:28 ` Pierre Weis
2004-07-22 17:03 ` William Lovas
2004-07-22 23:00 ` skaller
2004-07-23 3:32 ` William Lovas
2004-07-28 7:26 ` Pierre Weis
2004-07-28 8:06 ` skaller
2004-07-28 8:29 ` Daniel Bünzli
2004-07-28 9:13 ` Pierre Weis
2004-07-28 9:36 ` skaller
2004-07-28 9:38 ` skaller
2004-07-28 10:17 ` Jason Smith
2004-07-28 12:31 ` skaller
2004-07-21 20:41 ` [Caml-list] kprintf with user formatters Jon Harrop
2004-07-22 15:39 ` Pierre Weis
2004-07-22 22:16 ` [Caml-list] lazy evaluation: [Was: kprintf with user formatters] skaller
2004-07-22 22:42 ` [Caml-list] kprintf with user formatters skaller
2004-07-22 8:05 ` [Caml-list] wait instruction lehalle@miriad
2004-07-22 8:40 ` Olivier Andrieu
2004-07-22 10:35 ` lehalle@miriad
2004-07-22 10:33 ` Vitaly Lugovsky
2004-07-16 6:17 ` [Caml-list] kprintf with user formatters Pierre Weis
2004-07-16 17:14 ` Markus Mottl
2004-07-19 10:00 ` Pierre Weis
2004-07-16 6:02 ` Pierre Weis
2004-07-16 8:42 ` Damien
2004-07-19 9:00 ` Pierre Weis
2004-07-16 16:52 ` Markus Mottl
2004-07-19 9:28 ` Pierre Weis
2004-07-15 22:20 ` Pierre Weis
2004-07-15 23:01 ` Markus Mottl
2004-07-16 16:17 ` james woodyatt
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=d61254fb040716002313ae6402@mail.gmail.com \
--to=henridf@gmail.com \
--cc=basile.starynkevitch@inria.fr \
--cc=caml-list@inria.fr \
--cc=jean-christophe.filliatre@lri.fr \
--cc=pierre.weis@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