From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: suppress_checking Date: Tue, 23 Oct 2007 06:38:48 -0400 Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1193135944 22409 80.91.229.12 (23 Oct 2007 10:39:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Oct 2007 10:39:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Juanma Barranquero" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 23 12:39:04 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IkHA7-0006Xc-6l for ged-emacs-devel@m.gmane.org; Tue, 23 Oct 2007 12:39:03 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IkH9y-0005t7-SG for ged-emacs-devel@m.gmane.org; Tue, 23 Oct 2007 06:38:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IkH9t-0005sL-Vg for emacs-devel@gnu.org; Tue, 23 Oct 2007 06:38:50 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IkH9t-0005s6-Bc for emacs-devel@gnu.org; Tue, 23 Oct 2007 06:38:49 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IkH9t-0005rs-8Q for emacs-devel@gnu.org; Tue, 23 Oct 2007 06:38:49 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IkH9t-0007py-3O for emacs-devel@gnu.org; Tue, 23 Oct 2007 06:38:49 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1IkH9s-0003xB-Po; Tue, 23 Oct 2007 06:38:48 -0400 In-reply-to: (lekktu@gmail.com) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:81541 Archived-At: 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.