From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Adrien Nader <adrien@notk.org>
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>,
SF Markus Elfring <elfring@users.sourceforge.net>,
Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Clarification for the configuration of comparison functions
Date: Wed, 10 Sep 2014 08:38:55 -0400 [thread overview]
Message-ID: <CAN6ygO=YefN+8uucAvsNmAZVY9qVEf958kuo3HYGwPprQRYkcw@mail.gmail.com> (raw)
In-Reply-To: <20140910123749.GA23756@notk.org>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
That's good to know. Thanks for clarifying.
Yotam
On Wed, Sep 10, 2014 at 8:37 AM, Adrien Nader <adrien@notk.org> wrote:
> On Wed, Sep 10, 2014, Gerd Stolpmann wrote:
> > Am Mittwoch, den 10.09.2014, 08:07 -0400 schrieb Yotam Barnoy:
> > > Another reason is performance. The generic, polymorphic comparison
> > > function drops you out into C (which has a cost)
> >
> > Don't think so. compare doesn't allocate memory, so the few extra
> > instructions in caml_c_call for making allocation available from C
> > aren't required. Calling compare shouldn't be slower than calling a
> > function written in OCaml.
>
> And calling C from OCaml is _very_ fast. Too fast to be a concern.
>
> The other way round is slower, iirc maybe by a 100 factor.
>
> (you should benchmark yourself if any of these might be a concern)
>
> --
> Adrien Nader
>
[-- Attachment #2: Type: text/html, Size: 1341 bytes --]
next prev parent reply other threads:[~2014-09-10 12:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 8:56 SF Markus Elfring
2014-09-10 11:27 ` Gerd Stolpmann
2014-09-10 12:07 ` Yotam Barnoy
2014-09-10 12:26 ` Gerd Stolpmann
2014-09-10 12:37 ` Adrien Nader
2014-09-10 12:38 ` Yotam Barnoy [this message]
2014-09-10 12:41 ` Pippijn van Steenhoven
2014-09-10 12:51 ` Gerd Stolpmann
2014-09-10 12:56 ` Ben Millwood
[not found] ` <CAADdkeKquMWyHjQhgd2SOZYr9DaS2E+i3Ug5=xb25BK-+n16eQ@mail.gmail.com>
2014-09-10 12:44 ` Gerd Stolpmann
2014-09-10 20:56 ` SF Markus Elfring
2014-09-11 7:46 ` Francois Berenger
2014-09-11 8:10 ` SF Markus Elfring
2014-09-11 8:24 ` Francois Berenger
2014-09-11 8:33 ` SF Markus Elfring
2014-09-11 8:39 ` Frédéric Bour
2014-10-06 20:50 ` SF Markus Elfring
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='CAN6ygO=YefN+8uucAvsNmAZVY9qVEf958kuo3HYGwPprQRYkcw@mail.gmail.com' \
--to=yotambarnoy@gmail.com \
--cc=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=elfring@users.sourceforge.net \
--cc=info@gerd-stolpmann.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;
as well as URLs for NNTP newsgroup(s).