From: Paul Eggert <eggert@cs.ucla.edu>
To: Alan Mackenzie <acm@muc.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Excessive use of `eassert`
Date: Fri, 26 Jan 2024 00:06:56 -0800 [thread overview]
Message-ID: <4f92d945-d840-45df-818d-e813b9338e20@cs.ucla.edu> (raw)
In-Reply-To: <ZbEoEgC9jOl2DKkb@ACM>
On 2024-01-24 07:09, Alan Mackenzie wrote:
> The behaviour is not formally "undefined" and never has been.
Sure it is. In C, if you dereference a bad pointer the behavior is
undefined, which means anything can happen. On common platforms,
sometimes you'll get a crash and sometimes (as my example showed) you
won't, and this is true regardless of whether symbols-with-pos-enabled
is true. There has never been a guarantee in a normal build that XSYMBOL
(S) crashes when S is not a symbol, and none of the recent changes have
altered this fact about XSYMBOL.
next prev parent reply other threads:[~2024-01-26 8:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 22:35 Excessive use of `eassert` Stefan Monnier
2024-01-19 7:04 ` Eli Zaretskii
2024-01-19 13:01 ` Stefan Monnier
2024-01-19 15:02 ` Eli Zaretskii
2024-01-19 15:50 ` Stefan Monnier
2024-01-19 16:23 ` Eli Zaretskii
2024-01-19 17:44 ` Stefan Monnier
2024-01-19 19:42 ` Alan Mackenzie
2024-01-19 19:56 ` Eli Zaretskii
2024-01-21 1:41 ` Paul Eggert
2024-01-21 9:57 ` Eli Zaretskii
2024-01-21 20:35 ` Paul Eggert
2024-01-21 10:59 ` Alan Mackenzie
2024-01-22 5:19 ` Paul Eggert
2024-01-22 13:07 ` Stefan Monnier
2024-01-22 14:37 ` Alan Mackenzie
2024-01-23 7:51 ` Paul Eggert
2024-01-23 11:42 ` Alan Mackenzie
2024-01-24 1:04 ` Paul Eggert
2024-01-24 15:09 ` Alan Mackenzie
2024-01-26 8:06 ` Paul Eggert [this message]
2024-01-21 15:54 ` Stefan Monnier
2024-01-22 4:12 ` Paul Eggert
2024-01-22 13:20 ` Stefan Monnier
2024-01-23 8:15 ` Paul Eggert
2024-01-23 17:11 ` Stefan Monnier
2024-01-24 7:45 ` Paul Eggert
2024-01-23 18:16 ` Eli Zaretskii
2024-01-23 19:50 ` Stefan Monnier
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=4f92d945-d840-45df-818d-e813b9338e20@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).