From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: rudalics@gmx.at, kalman.reti@gmail.com, emacs-devel@gnu.org
Subject: Re: mark_object crash in 22.1 and latest CVS (as of tonight)
Date: Sat, 17 Nov 2007 22:08:44 -0500 [thread overview]
Message-ID: <jwvy7cwb6d7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1ItRgw-0006mW-2n@fencepost.gnu.org> (Richard Stallman's message of "Sat, 17 Nov 2007 12:42:50 -0500")
> The `evaporate' option is inherently dangerous since it reclaims the
> marker object forcefully without checking that nobody else is holding on
> to it, even tho it comes from a plain normal argument and the caller may
> very well have kept another ref to it somewhere.
> There are low-level constructs in Emacs that can crash Emacs if misused.
> This mere fact is not enough reason to get rid of it.
It's an "optimization" and nothing more. In my book, if an optimization
is unsafe, it had better make a good case for itself. As it stands
I see no evidence that this optimization is ever useful. As long as
nobody can show us numbers that demonstrate a measurable performance
impact, I think we're better off without this optimization.
Stefan
next prev parent reply other threads:[~2007-11-18 3:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16af2f430711081955j3d5e6745gc0f7a50e02d9a892@mail.gmail.com>
[not found] ` <16af2f430711090332x39c8c768gb01d1dc6a0e4f427@mail.gmail.com>
2007-11-11 5:22 ` mark_object crash in 22.1 and latest CVS (as of tonight) Richard Stallman
2007-11-12 11:40 ` Kalman Reti
2007-11-12 22:03 ` Stefan Monnier
2007-11-13 0:30 ` Kalman Reti
2007-11-13 20:03 ` Richard Stallman
2007-11-14 17:39 ` Kalman Reti
2007-11-14 18:51 ` Stefan Monnier
2007-11-15 1:00 ` Kalman Reti
2007-11-15 17:09 ` Richard Stallman
2007-11-16 12:05 ` Kalman Reti
2007-11-16 14:07 ` Kalman Reti
2007-11-16 17:28 ` martin rudalics
2007-11-16 17:56 ` Kalman Reti
2007-11-17 4:54 ` Richard Stallman
2007-11-17 5:43 ` Kalman Reti
2007-11-16 19:04 ` Stefan Monnier
2007-11-16 21:52 ` martin rudalics
2007-11-16 22:09 ` Stefan Monnier
2007-11-16 22:16 ` Stefan Monnier
2007-11-16 23:59 ` Kalman Reti
2007-11-17 4:25 ` Stefan Monnier
2007-11-17 17:42 ` Richard Stallman
2007-11-18 3:08 ` Stefan Monnier [this message]
2007-11-18 22:45 ` Richard Stallman
2007-11-18 23:22 ` David Kastrup
2007-11-19 7:50 ` Stefan Monnier
2007-11-19 19:03 ` Richard Stallman
2007-11-17 4:53 ` Richard Stallman
2007-11-15 3:08 ` Richard Stallman
2007-11-15 8:38 ` Kalman Reti
2007-11-16 20:48 ` Kalman Reti
2007-11-16 21:59 ` Stefan Monnier
2007-11-16 23:09 ` martin rudalics
2008-02-04 11:35 ` buffer-undo-list (was: mark_object crash in 22.1 and latest CVS (as of tonight)) Johan Bockgård
2008-02-04 21:44 ` buffer-undo-list Stefan Monnier
2008-02-11 17:58 ` buffer-undo-list Stefan Monnier
2007-11-13 5:10 ` mark_object crash in 22.1 and latest CVS (as of tonight) Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvy7cwb6d7.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=kalman.reti@gmail.com \
--cc=rms@gnu.org \
--cc=rudalics@gmx.at \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).