From: Richard Stallman <rms@gnu.org>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: suppress_checking
Date: Tue, 23 Oct 2007 06:38:48 -0400 [thread overview]
Message-ID: <E1IkH9s-0003xB-Po@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b0710220859t2bcf3aa1q259e34e5f8efef88@mail.gmail.com> (lekktu@gmail.com)
Is there any point to the variable suppress_checking, or is it leftover code?
Since eassert uses CHECK, this offers the possibility to turn off
eassert checking at run time. However, eassert is no-op'd by default
at compile time, because ENABLE_CHECKING is normally not defined.
I don't see that it is useful, but I also don't see a point
in deleting it.
suppress_checking is implemented in a funny way: the expression to be
tested is computed and then ignored. That would make sense if we were
concerned about function calls and side effects in the expression to
be tested. However, if there were any, ENABLE_CHECKING would not work.
So we may as well test suppress_checking first.
next prev parent reply other threads:[~2007-10-23 10:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 15:59 suppress_checking Juanma Barranquero
2007-10-23 10:38 ` Richard Stallman [this message]
2007-10-23 10:59 ` suppress_checking Juanma Barranquero
2007-10-24 2:49 ` suppress_checking Richard Stallman
2007-10-24 8:56 ` suppress_checking Juanma Barranquero
2007-10-29 17:51 ` suppress_checking Ken Raeburn
2007-10-29 18:16 ` suppress_checking Ken Raeburn
2007-10-29 22:49 ` suppress_checking Juanma Barranquero
2007-10-29 19:06 ` suppress_checking Stefan Monnier
2007-10-29 20:47 ` suppress_checking Ken Raeburn
2007-10-30 5:24 ` suppress_checking Richard Stallman
2007-11-01 3:25 ` suppress_checking Ken Raeburn
2007-11-01 19:04 ` suppress_checking 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=E1IkH9s-0003xB-Po@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/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).