From: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: valid_pointer_p
Date: Sat, 29 Jul 2006 12:45:58 +0200 [thread overview]
Message-ID: <je4px04rkp.fsf@sykes.suse.de> (raw)
In-Reply-To: <u64hgd7us.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 Jul 2006 13:27:07 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Can someone ``in the know'' please explain what clever idea is behind
> the function valid_pointer_p, and whether that idea is supposed to be
> portable?
While I agree that the function is non-portable at best, it is only used
for debugging (called via safe_debug_print by some gdb macros), nothing
inside Emacs is calling it.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-07-29 10:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 10:27 valid_pointer_p Eli Zaretskii
2006-07-29 10:45 ` Andreas Schwab [this message]
2006-07-29 12:16 ` valid_pointer_p Eli Zaretskii
2006-07-30 0:05 ` valid_pointer_p Kim F. Storm
2006-07-30 3:16 ` valid_pointer_p Eli Zaretskii
2006-07-30 22:13 ` valid_pointer_p Kim F. Storm
2006-07-31 3:21 ` valid_pointer_p Eli Zaretskii
2006-07-31 8:30 ` valid_pointer_p Andreas Schwab
2006-07-31 17:10 ` valid_pointer_p Eli Zaretskii
2006-07-31 17:56 ` valid_pointer_p Andreas Schwab
2006-07-31 9:01 ` valid_pointer_p Kim F. Storm
2006-08-05 13:04 ` valid_pointer_p Eli Zaretskii
2006-08-05 13:09 ` valid_pointer_p Eli Zaretskii
2006-08-05 22:11 ` valid_pointer_p Kim F. Storm
2006-08-06 3:29 ` valid_pointer_p Eli Zaretskii
2006-08-11 22:58 ` valid_pointer_p Kim F. Storm
2006-08-12 11:06 ` valid_pointer_p Eli Zaretskii
2006-08-12 12:36 ` valid_pointer_p Andreas Schwab
2006-08-12 14:39 ` valid_pointer_p Eli Zaretskii
2006-08-12 20:19 ` valid_pointer_p Kim F. Storm
2006-08-12 21:56 ` valid_pointer_p Eli Zaretskii
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=je4px04rkp.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@gnu.org \
/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.