From: Alessandro Baretta <a.baretta@studio.baretta.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Question on performance/style issue
Date: Fri, 24 Feb 2006 20:25:26 +0100 [thread overview]
Message-ID: <43FF5DA6.6000600@studio.baretta.com> (raw)
In-Reply-To: <20060224190501.GA27740@fork.recoil.org>
Anil Madhavapeddy wrote:
>>>x ++ f ++ g ++ h
>>
>>What is the impact of the this programming style on execution performance?
>
>
>>From a GC point of view, this is better than the alternative of
> splitting up the calls into separate let bindings. It's used in
> the OCaml sources to make some long call-chains look nicer.
Ah, yes, it makes one's code dense and legible at once. What I'm asking is
whether the call to (++) manages to get compiled away--that is, reduced to its
definition--or if I pay for the additional jump every time. In this latter case
I might have to renounce the (++) operator in inner loops where I need to
squeeze out every last bit of performance.
Alex
--
*********************************************************************
Ing. Alessandro Baretta
Studio Baretta
http://studio.baretta.com/
Consulenza Tecnologica e Ingegneria Industriale
Technological Consulting and Industrial Engineering
tel. +39 02 370 111 55
fax. +39 02 370 111 54
next prev parent reply other threads:[~2006-02-24 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 15:52 Alessandro Baretta
2006-02-24 19:05 ` [Caml-list] " Anil Madhavapeddy
2006-02-24 19:25 ` Alessandro Baretta [this message]
2006-02-25 11:14 ` Andrej Bauer
2006-02-27 22:37 ` David M. Cooke
2006-02-27 23:49 ` [Caml-list] " David Brown
2006-02-28 12:02 ` Alessandro Baretta
2006-02-28 12:04 ` [Caml-list] " Alessandro Baretta
2006-03-01 5:45 ` Nathaniel Gray
2006-03-01 8:34 ` Alessandro Baretta
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=43FF5DA6.6000600@studio.baretta.com \
--to=a.baretta@studio.baretta.com \
--cc=anil@recoil.org \
--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;
as well as URLs for NNTP newsgroup(s).