caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jonathan Protzenko <jonathan.protzenko@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Nicolas Ojeda Bar <nicolas.ojeda.bar@lexifi.com>,
	OCaml Mailing List <caml-list@inria.fr>,
	Rodolphe Lepigre <rodolphe.lepigre@univ-savoie.fr>
Subject: Re: [Caml-list] Printf.sprintf "%a"
Date: Sat, 9 Jul 2016 00:26:22 -0700	[thread overview]
Message-ID: <48a9be2f-3ba9-099b-c65e-548028e012aa@gmail.com> (raw)
In-Reply-To: <CAPFanBG-4rwc-VNDbDOtRqXtsSSLDc+nd30ehU=9UnMa-4sHTA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]

Basically what we did for Mezzo. All printers are intended to work with 
Buffer.t and %a; then, define a bunch of variants of fprintf, iprintf, 
kprintf, sprintf, eprintf that work with Buffer.t

https://github.com/protz/mezzo/blob/master/lib/MzString.ml

On 7/8/16 3:53 AM, Gabriel Scherer wrote:
> For non-formatted printing, I find that bprintf (using Buffer.t) is 
> the more composable primitive.
>
> On Fri, Jul 8, 2016 at 4:16 AM, Rodolphe Lepigre 
> <rodolphe.lepigre@univ-savoie.fr 
> <mailto:rodolphe.lepigre@univ-savoie.fr>> wrote:
>
>     Thanks for your answer!
>
>     > I don't think this is possible with Printf.  But if you can
>     switch to Format
>     > you can use Format.asprintf instead.
>
>     Yes, I know it is possible to use Format. This is actually what I
>     am doing
>     currently! However, I am not using any of the formating features,
>     so I'd
>     like to switch to Printf to avoid going from channels to
>     formatters all the
>     time...
>
>     >> Dear list,
>     >>
>     >> If I define two values
>     >>
>     >>   val p : type out_channel -> blop -> unit
>     >>   val e : blop
>     >>
>     >> then I can do something like
>     >>
>     >>   Printf.printf "%a" p e
>     >>
>     >> but I can't find a way to do something like
>     >>
>     >>   Printf.sprintf "%a" p e
>     >>
>     >> which is not well-typed. Is there any trick that I can use to avoid
>     >> changing the type of [p] to [blop -> string]?
>     >>
>     >> Cheers,
>     >>
>     >> Rodolphe
>
>     Cheers,
>
>     Rodolphe
>     --
>     Rodolphe Lepigre
>     LAMA, Université Savoie Mont Blanc, FRANCE
>     http://lama.univ-smb.fr/~lepigre/
>     <http://lama.univ-smb.fr/%7Elepigre/>
>     On 08/07/2016 10:08, Nicolas Ojeda Bar wrote:
>
>     --
>     Caml-list mailing list.  Subscription management and archives:
>     https://sympa.inria.fr/sympa/arc/caml-list
>     Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>     Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>


[-- Attachment #2: Type: text/html, Size: 4413 bytes --]

      reply	other threads:[~2016-07-09  7:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08  8:01 Rodolphe Lepigre
2016-07-08  8:08 ` Nicolas Ojeda Bar
2016-07-08  8:16   ` Rodolphe Lepigre
2016-07-08 10:53     ` Gabriel Scherer
2016-07-09  7:26       ` Jonathan Protzenko [this message]

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=48a9be2f-3ba9-099b-c65e-548028e012aa@gmail.com \
    --to=jonathan.protzenko@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    --cc=nicolas.ojeda.bar@lexifi.com \
    --cc=rodolphe.lepigre@univ-savoie.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;
as well as URLs for NNTP newsgroup(s).