From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: storm@cua.dk, emacs-devel@gnu.org, handa@m17n.org
Subject: Re: Potential GC-related problems in compose_chars_in_text
Date: Mon, 19 Sep 2005 09:43:14 -0400 [thread overview]
Message-ID: <8764sxyy63.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1EGcuI-0003hJ-Ga@fencepost.gnu.org> (Richard M. Stallman's message of "Sat, 17 Sep 2005 09:39:06 -0400")
> Actually, it often happens that things like ENABLE_CHECKING add assert
> statements in the macro expansion which causes the args to be used more
> than once.
> As far as I can see, ENABLE_CHECKING has no such effect anywhere.
It does.
See the definition of XSET:
#define XSET(var, type, ptr) \
(eassert (XTYPE (ptr) == 0), /* Check alignment. */ \
(var) = ((EMACS_INT) (type)) | ((EMACS_INT) (ptr)))
> And there is only one definition of SREF.
Yes, currently SREF does not currently "suffer" from this problem, but it
may become useful at some point in the future to add some kind of check on
the second or of SREF.
I have myself bumped into such problem when I try to add such checks in XINT
(which currently doesn't check that its arg is indeed an integer).
Stefan
next prev parent reply other threads:[~2005-09-19 13:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 0:58 potential bug in display_mode_element? Kenichi Handa
2005-09-12 8:04 ` Kim F. Storm
2005-09-12 11:54 ` Kenichi Handa
2005-09-12 12:41 ` Potential GC-related problems in compose_chars_in_text Kim F. Storm
2005-09-13 1:08 ` Kenichi Handa
2005-09-13 15:54 ` Richard M. Stallman
2005-09-14 7:29 ` Kenichi Handa
2005-09-15 2:41 ` Richard M. Stallman
2005-09-15 4:21 ` Kenichi Handa
2005-09-16 1:01 ` Richard M. Stallman
2005-09-16 15:39 ` Stefan Monnier
2005-09-17 13:39 ` Richard M. Stallman
2005-09-19 13:43 ` Stefan Monnier [this message]
2005-09-12 15:34 ` potential bug in display_mode_element? Richard M. 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8764sxyy63.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=storm@cua.dk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.