Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
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: 25 Mar 1999 15:52:05 -0500	[thread overview]
Message-ID: <ya2vhfpcmx6.fsf@zarya.maya.com> (raw)
In-Reply-To: Christian Lindig's message of "Thu, 25 Mar 1999 14:29:01 +0100"

Christian Lindig <lindig@ips.cs.tu-bs.de> writes:

> The suggested functional approach to printf has another possible
> drawback:  when you want to express all the options like "%5.5f"
> possible in C style printf formatting you need a whole bunch of
> functions.  Since OCaml has no overloading a single `float' function
> for floats can not capture them all. 

Yes, but you can still get the formatting features you want by having
both formats that take arguments (like "lit") and also higher-order
formats (for example, a format which truncates whatever format it is
given to a specific string length, or a format that right justifies
within a certain length, or etc.)

In fact, the system is more powerful precisely because you can do
things like this to extend the system.  Not only can you do %5.5f, you
could also make something to display the float in binary, or to
display the fraction as a vulgar fraction symbol (i.e. ½).

John.




  reply	other threads:[~1999-03-26 13:13 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
1999-03-25 13:29         ` Christian Lindig
1999-03-25 20:52           ` John Prevost [this message]
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=ya2vhfpcmx6.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