From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Building Emacs overflowed pure space Date: Fri, 21 Jul 2006 21:48:55 +0200 Message-ID: <85hd1ayc0o.fsf@lola.goethe.zz> References: <7dbe73ed0607180138x35e9d9bft3e42f20cb369795c@mail.gmail.com> <200607181929.k6IJTZN9028639@jane.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 1153511370 28589 80.91.229.2 (21 Jul 2006 19:49:30 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 21 Jul 2006 19:49:30 +0000 (UTC) Cc: teirllm@dms.auburn.edu, ralphm@members.fsf.org, emacs-devel@gnu.org, "Kim F. Storm" , mituharu@math.s.chiba-u.ac.jp, mathias.dahl@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 21 21:49:28 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G40zw-0004i5-Uu for ged-emacs-devel@m.gmane.org; Fri, 21 Jul 2006 21:49:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G40zw-0001Ww-AL for ged-emacs-devel@m.gmane.org; Fri, 21 Jul 2006 15:49:20 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G40zl-0001Wh-8h for emacs-devel@gnu.org; Fri, 21 Jul 2006 15:49:09 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G40zj-0001WU-Ab for emacs-devel@gnu.org; Fri, 21 Jul 2006 15:49:08 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G40zj-0001WP-3t for emacs-devel@gnu.org; Fri, 21 Jul 2006 15:49:07 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G410B-0006mH-Of; Fri, 21 Jul 2006 15:49:35 -0400 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1G40za-0000BD-PL; Fri, 21 Jul 2006 15:48:59 -0400 Original-Received: by lola.goethe.zz (Postfix, from userid 1002) id 4FF471C4D3B9; Fri, 21 Jul 2006 21:48:55 +0200 (CEST) Original-To: rms@gnu.org In-Reply-To: (Richard Stallman's message of "Fri, 21 Jul 2006 15:36:56 -0400") 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 Xref: news.gmane.org gmane.emacs.devel:57444 Archived-At: Richard Stallman writes: > But to follow your suggestion, why don't we just have _one_ generic > uninterned "tmp" symbol for all such uses. > > We could do that. It would work. > > It would be a little better to have a list of ten of them and pick at > random. That would facilitate examining values in the Lisp debugger > on those occasions when you really want to. I don't see how. They are uninterned, after all. And "picking at random" means that it becomes unpredictable what loop combinations will happen to be debuggable, and what combinations will not. And it will change from compilation to compilation. I don't like that at all. Frankly speaking: I don't know what we are supposed to buy ourselves if a loop body can access its internal variable by (symbol-value tmp-loop-var) instead of just tmp-loop-var. It seems like a pointless exercise in obfuscation. It does not buy us any encapsulation, and makes debugging and understanding the code harder when disassembling it. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum