From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: xassert in dispextern.h Date: Wed, 02 Mar 2005 21:29:15 -0500 Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1109817230 3491 80.91.229.2 (3 Mar 2005 02:33:50 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 3 Mar 2005 02:33:50 +0000 (UTC) Cc: miles@gnu.org, snogglethorpe@gmail.com, emacs-devel@gnu.org, jasonr@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 03 03:33:49 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D6g8d-0006LM-HM for ged-emacs-devel@m.gmane.org; Thu, 03 Mar 2005 03:32:31 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D6gQe-0007YL-Kp for ged-emacs-devel@m.gmane.org; Wed, 02 Mar 2005 21:51:08 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D6gPb-0007Gs-VF for emacs-devel@gnu.org; Wed, 02 Mar 2005 21:50:04 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D6gPU-0007CV-H2 for emacs-devel@gnu.org; Wed, 02 Mar 2005 21:49:56 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D6gPU-0007AQ-DN for emacs-devel@gnu.org; Wed, 02 Mar 2005 21:49:56 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D6g5W-0004SD-BK for emacs-devel@gnu.org; Wed, 02 Mar 2005 21:29:18 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1D6g5T-0001QC-0s; Wed, 02 Mar 2005 21:29:15 -0500 Original-To: storm@cua.dk (Kim F. Storm) In-reply-to: (storm@cua.dk) 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:34113 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34113 I'll suggest that we leave the xassert in there for 2 more weeks -- just in case something serious pops up -- and then remove them again and focus on finishing the release. Since you're doing most of the work on debugging the display bugs, my decision is to follow your judgment. Miles wrote: The right answer is to change those xasserts (and _only_ those) which cause a problem or test something silly or are insanely inefficient [99% are quite efficient] to use some other macro, like "gdassert" or something, and make gdassert dependent on GLYPH_DEBUG. First let's just turn them off. Afterward, if you identify the set that can reasonably and usefully always be on, we can follow your suggestion.