From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: oliver <oliver@first.in-berlin.de>
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 15:04:56 +0200 [thread overview]
Message-ID: <CAPFanBG4e8khmYzSePOYO3rze=nAu+h+DM3NqSt_s5SwB_GLaQ@mail.gmail.com> (raw)
In-Reply-To: <20120625113936.GE1837@siouxsie>
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.).
Why are we having this conversation?
On Mon, Jun 25, 2012 at 1:39 PM, oliver <oliver@first.in-berlin.de> wrote:
> On Mon, Jun 25, 2012 at 02:09:47AM +0200, Diego Olivier Fernandez Pons wrote:
> [...]
>> There is a little trick however... I work mostly in combinatorial
>> optimization. If your input takes more than 1s to read or write, it
>> will take the age of the universe to solve given combinatorial
>> algorithms are exponential in the input size. And there is little
>> point in putting a printf on a branch-and-bound algorithm that opens
>> 10^6 nodes.
> [...]
>
> This looks like you really should use the Buffer-module.
>
> Ciao,
> Oliver
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2012-06-25 13:05 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 [this message]
2012-06-25 14:25 ` oliver
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='CAPFanBG4e8khmYzSePOYO3rze=nAu+h+DM3NqSt_s5SwB_GLaQ@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=dofp.ocaml@gmail.com \
--cc=lukstafi@gmail.com \
--cc=oliver@first.in-berlin.de \
/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