From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: hash-table-{to, from}-alist Date: Tue, 02 Dec 2008 08:21:27 -0600 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <86r64qbqu0.fsf@lifelogs.com> References: <863aknitfg.fsf@lifelogs.com> <86bpwe9su5.fsf@lifelogs.com> <867i6z1jo5.fsf_-_@lifelogs.com> <86ej14vhvg.fsf@lifelogs.com> <20081122054510.GA28298@tomas> <873ahkkkt5.fsf@xemacs.org> <20081122152126.GA4142@tomas> <87vdufk6do.fsf@xemacs.org> <867i6tt4yz.fsf@lifelogs.com> <87bpw4k1z6.fsf@xemacs.org> <86bpw3d829.fsf@lifelogs.com> <87k5ari5jh.fsf@xemacs.org> <86prkiiia2.fsf@lifelogs.com> <86ej0ygr5j.fsf@lifelogs.com> <877i6qqam5.fsf@uwakimon.sk.tsukuba.ac.jp> <86d4gbd0ld.fsf@lifelogs.com> <87myffymj3.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1228227795 22891 80.91.229.12 (2 Dec 2008 14:23:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 2 Dec 2008 14:23:15 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 02 15:24:19 2008 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 1L7WAP-0001qw-21 for ged-emacs-devel@m.gmane.org; Tue, 02 Dec 2008 15:23:57 +0100 Original-Received: from localhost ([127.0.0.1]:44241 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L7W9E-0007nz-L4 for ged-emacs-devel@m.gmane.org; Tue, 02 Dec 2008 09:22:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L7W8r-0007lo-7d for emacs-devel@gnu.org; Tue, 02 Dec 2008 09:22:21 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L7W8p-0007lc-CY for emacs-devel@gnu.org; Tue, 02 Dec 2008 09:22:20 -0500 Original-Received: from [199.232.76.173] (port=40873 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L7W8p-0007lZ-64 for emacs-devel@gnu.org; Tue, 02 Dec 2008 09:22:19 -0500 Original-Received: from main.gmane.org ([80.91.229.2]:57639 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1L7W8o-0005Xi-Jc for emacs-devel@gnu.org; Tue, 02 Dec 2008 09:22:19 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1L7W8m-0006t8-QQ for emacs-devel@gnu.org; Tue, 02 Dec 2008 14:22:16 +0000 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Dec 2008 14:22:16 +0000 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Dec 2008 14:22:16 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 46 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:10hTSk2vgdh4ncyhwgkqkwjTFHc= X-detected-operating-system: by monty-python.gnu.org: GNU/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:106425 Archived-At: On Tue, 02 Dec 2008 18:05:52 +0900 "Stephen J. Turnbull" wrote: SJT> Ted Zlatanov writes: >> Can you and Stefan figure out whether to have print-readably or >> not? I was against it, and Stefan supported that. But let's see >> the pro argument and discuss this. SJT> The pro argument is that unless you're debugging the hash table, it's SJT> a PITA to have a hash table that gets recursively passed to each SJT> function down the line taking up 20 screens for each frame in a SJT> backtrace. "Not debugging the hash table" is the overwhelmingly SJT> common occurance for me; usually I'm more interested in where in the SJT> stack the value I'm going to be puthash'ing turned from gold into SJT> garbage. OTOH, about half the time when I've got a chartable in the SJT> stack, the chartable is buggy (in my experience almost all chartables SJT> are write-once). Isn't the same argument valid for lists? At least in the Emacs backtrace, lists get shortened for display; I don't know if that's done at the print level or at the display level. If it's at the display level, a lot of cycles are wasted for large lists. Basically I want to treat hashtables like lists as much as possible for printing and reading, so print-readably would introduce inconsistency. Otherwise I agree with your argument, I am just reluctant to make hashtables an exception to the general print behavior. >> Will the current state of things cause XEmacs breakage anywhere? SJT> No. This is a user interface thing. If I'm right, XEmacs will get a SJT> mild popularity boost if you always print the hash table. I'm not SJT> going to complain about that! ;-) Heh. >> One idea I had is to check if print-readably is bound; if not then >> we act as if it was bound and t. That will DTRT in GNU Emacs and >> in XEmacs, I hope. SJT> Hm? XEmacs already has the feature in C; your code will either get SJT> ignored in XEmacs syncs, or its algorithms will be ported to our C SJT> code. Definitely not something for you to worry about. Great. Ted