From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] OCaml and Boehm
Date: Sat, 11 Apr 2009 15:27:58 +0100 [thread overview]
Message-ID: <200904111527.58652.jon@ffconsultancy.com> (raw)
In-Reply-To: <4a708d20904110711i199ef805h611a04d823c8fb51@mail.gmail.com>
On Saturday 11 April 2009 15:11:38 Lukasz Stafiniak wrote:
> (Another question which is off-topic for this list is whether smart
> pointers in their situation would be a high performance hit.)
Depends what "their situation" is. :-)
Smart pointers are adequate for specific domains where performance is
unimportant and cycles cannot occur, like handling the destruction of GUI
elements. In general, smart pointers are orders of magnitude slower than
garbage collection because they bump values in the heap every time they
change hands.
Also, don't forget that many people incorrectly claim that smart pointers
deallocate at the earliest possible point when, in fact, they typically keep
values alive longer than necessary.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next prev parent reply other threads:[~2009-04-11 14:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 20:13 Lukasz Stafiniak
2009-04-11 9:46 ` [Caml-list] " Basile STARYNKEVITCH
2009-04-11 10:42 ` Jon Harrop
[not found] ` <4a708d20904110511o7d390807r3d29400cf96d6f35@mail.gmail.com>
[not found] ` <49E09C2D.4080906@starynkevitch.net>
2009-04-11 14:11 ` Lukasz Stafiniak
2009-04-11 14:27 ` Jon Harrop [this message]
2009-04-11 14:40 ` Lukasz Stafiniak
2009-04-11 20:40 ` Jon Harrop
2009-04-11 15:03 ` Basile STARYNKEVITCH
2009-04-11 20:41 ` Jon Harrop
2009-04-13 9:42 ` Christoph Bauer
2009-04-13 13:15 ` Lukasz Stafiniak
2009-04-14 5:25 ` Goswin von Brederlow
2009-04-12 3:34 ` Goswin von Brederlow
2009-04-12 12:09 ` Lukasz Stafiniak
2009-04-13 17:36 ` Xavier Leroy
2009-04-11 19:17 Ed Keith
2009-04-11 20:36 ` Jon Harrop
2009-04-12 3:25 ` 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=200904111527.58652.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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