From: Xavier Leroy <xavier.leroy@inria.fr>
To: Vaibhav Bhandari <vaibhav@cse.ucsc.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Function Indirection overhead?
Date: Fri, 24 Jan 2003 11:34:11 +0100 [thread overview]
Message-ID: <20030124113411.C9454@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.GSO.4.44.0301232319440.17524-100000@sundance.cse.ucsc.edu>; from vaibhav@cse.ucsc.edu on Thu, Jan 23, 2003 at 11:21:05PM -0800
> I am not sure, if in ocaml we write
>
> let f = Hop.a;
>
> where f and Hop.a are methods, does the compiler "short-circuit" the call,
> or not?
Yes, it does. Applications of function f will go straight to the code
for Hop.a. Contrast this with
let f x = Hop.a x
where an additional call (from f to Hop.a) would occur.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-01-24 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 7:21 Vaibhav Bhandari
2003-01-24 10:34 ` Xavier Leroy [this message]
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=20030124113411.C9454@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=vaibhav@cse.ucsc.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).