From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: xassert in dispextern.h Date: Wed, 02 Mar 2005 10:13:34 +0100 Message-ID: References: <200503012317.j21NHIj20008@raven.dms.auburn.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1109756482 22409 80.91.229.2 (2 Mar 2005 09:41:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 2 Mar 2005 09:41:22 +0000 (UTC) Cc: jasonr@gnu.org, emacs-devel@gnu.org, Luc Teirlinck , miles@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 02 10:41:21 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D6QKX-00036T-C6 for ged-emacs-devel@m.gmane.org; Wed, 02 Mar 2005 10:39:45 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D6QdG-0007qI-Hx for ged-emacs-devel@m.gmane.org; Wed, 02 Mar 2005 04:59:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D6QAd-0002Hs-Q0 for emacs-devel@gnu.org; Wed, 02 Mar 2005 04:29:32 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D6QAa-0002HK-Qo for emacs-devel@gnu.org; Wed, 02 Mar 2005 04:29:30 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D6Q9F-0001pm-PC for emacs-devel@gnu.org; Wed, 02 Mar 2005 04:28:05 -0500 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.34) id 1D6Pv8-000273-86 for emacs-devel@gnu.org; Wed, 02 Mar 2005 04:13:30 -0500 Original-Received: (qmail 45283 invoked from network); 2 Mar 2005 09:13:29 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 2 Mar 2005 09:13:29 -0000 Original-To: snogglethorpe@gmail.com In-Reply-To: (Miles Bader's message of "Wed, 2 Mar 2005 09:35:48 +0900") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:34045 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34045 Miles Bader writes: >> The right answer is to change those xasserts (and _only_ those) which >> cause a problem or test something silly or are insanely inefficient >> >> How do we find and recognize all of those? > > In order to demonstrate that the majority are superfluous, one has to > actually be able to make exactly the same sort of judgement for each > xassert -- so I'm saying, if you can make that judgement, then why not ^^^ There's that "YOU" again -- please be precise -- who is that? If nobody can or will to that (and nobody has volounteered to do it yet) -- then it will not happen, and the xasserts continue to be a source of irrelevant crashes for users (who as David points out have to rely on CVS emacs for their work). > use it on a case-by-case basis to get the best of both worlds? > If, on the other hand, it's the case that nobody can make that > judgement for most xasserts, then nobody is in a position to say > xassert can safely be disabled either. Well, the experience from enabling xasserts definitely shows that they cannot be "safely enabled". -- Kim F. Storm http://www.cua.dk