caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent@snarc.org>
To: Jonathan Bryant <jtbryant@valdosta.edu>
Cc: "Quôc Peyrot" <chojin@lrde.epita.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] precision not working properly for strings in Printf?
Date: Wed, 27 Jun 2007 10:34:02 +0200	[thread overview]
Message-ID: <20070627083401.GA32745@snarc.org> (raw)
In-Reply-To: <8503CBAB-EF9E-4CF0-89A8-2F6E454CF4DC@valdosta.edu>

On Wed, Jun 27, 2007 at 12:11:01AM -0400, Jonathan Bryant wrote:
> The OCaml standard library isn't glibc.  The implementation of the  
> Printf/Scanf modules is custom, OCaml specific and tied into the  
> compiler, so one should not assume the behave the same way.  They are  
> not simply wrappers.  As a matter of fact, they have several other  
> differences from the glibc printf family of functions (look at the  
> conversion specifiers in the docs).
> 
> >As said above, this is not how printf is working in the glibc (at  
> >least on linux and Mac OS X). Any clue why the same convention has  
> >not been followed?
> 
> See above.

What about reading before replying ?
Your "explanation" certainly doesn't answer his question.
whether or not it's the same *implementation* doesn't answer why ocaml
printf choosed a different *convention* (specially on this case which I
don't see any contradiction in the way ocaml works).

Cheers,
-- 
Vincent Hanquez


  reply	other threads:[~2007-06-27  8:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27  3:18 Quôc Peyrot
2007-06-27  3:38 ` [Caml-list] " Jonathan Bryant
2007-06-27  3:48   ` Quôc Peyrot
2007-06-27  4:11     ` Jonathan Bryant
2007-06-27  8:34       ` Vincent Hanquez [this message]
2007-06-27  9:53         ` Jonathan Bryant
2007-06-27 11:08           ` Quôc Peyrot
2007-07-03  1:14           ` David Thomas
2007-06-27 10:46         ` Quôc Peyrot

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=20070627083401.GA32745@snarc.org \
    --to=vincent@snarc.org \
    --cc=caml-list@inria.fr \
    --cc=chojin@lrde.epita.fr \
    --cc=jtbryant@valdosta.edu \
    /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).