From: oliver <oliver@first.in-berlin.de>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Diego Olivier Fernandez Pons <dofp.ocaml@gmail.com>,
Lukasz Stafiniak <lukstafi@gmail.com>,
OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] print_int is too slow
Date: Mon, 25 Jun 2012 16:25:37 +0200 [thread overview]
Message-ID: <20120625142537.GB4794@siouxsie> (raw)
In-Reply-To: <CAPFanBG4e8khmYzSePOYO3rze=nAu+h+DM3NqSt_s5SwB_GLaQ@mail.gmail.com>
On Mon, Jun 25, 2012 at 03:04:56PM +0200, Gabriel Scherer wrote:
> I don't see the point of using Buffer if he does not intend to
> postprocess the output; why store the string in full? Just avoid
> print_newline() if you don't want buffering, print_string "\n" will be
> fine (or Printf.printf without %!, etc.).
I answered on the topic of huge input data.
I doubt that the example which was used here,
with some printng-statements,
will be used all the time.
As it was mentioned, it is some OCaml learning stuff,
and one day it might become more complex and the data read and written
will be more.
Then string-append in the reading part, wihout Buffer module will
become a bottleneck.
> Why are we having this conversation?
Why are you asking this question?
Ciao,
Oliver
next prev parent reply other threads:[~2012-06-25 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 18:40 Diego Olivier Fernandez Pons
2012-06-24 18:59 ` Gabriel Scherer
2012-06-24 19:08 ` Diego Olivier Fernandez Pons
2012-06-24 19:18 ` Oliver Bandel
2012-06-24 19:26 ` Diego Olivier Fernandez Pons
2012-06-24 19:48 ` Adrien
[not found] ` <20120624.220220.2022399462583597382.Christophe.Troestler@umons.ac.be>
2012-06-24 22:19 ` Diego Olivier Fernandez Pons
2012-06-24 23:06 ` Lukasz Stafiniak
2012-06-24 23:52 ` Anthony Tavener
2012-06-25 0:09 ` Diego Olivier Fernandez Pons
2012-06-25 11:39 ` oliver
2012-06-25 13:04 ` Gabriel Scherer
2012-06-25 14:25 ` oliver [this message]
2012-06-25 17:31 ` Florian Weimer
2012-06-25 10:07 ` Goswin von Brederlow
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=20120625142537.GB4794@siouxsie \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
--cc=dofp.ocaml@gmail.com \
--cc=gabriel.scherer@gmail.com \
--cc=lukstafi@gmail.com \
/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).