From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3971 invoked by alias); 25 Sep 2002 03:01:34 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3963 invoked from network); 25 Sep 2002 03:01:33 -0000 Received: from unknown (HELO zenia.red-bean.com) (66.244.67.22) by sources.redhat.com with SMTP; 25 Sep 2002 03:01:33 -0000 Received: (from jimb@localhost) by zenia.red-bean.com (8.11.6/8.11.6) id g8P2kN525412; Tue, 24 Sep 2002 21:46:23 -0500 To: David Carlton Cc: Daniel Berlin , Daniel Jacobowitz , gdb@sources.redhat.com Subject: Re: suggestion for dictionary representation References: <6FDBFE18-CF55-11D6-BA45-000393575BCC@dberlin.org> From: Jim Blandy Date: Tue, 24 Sep 2002 20:01:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2.90 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-09/txt/msg00392.txt.bz2 David Carlton writes: > And it's entirely reasonable to think of 'N' as a constant. Or > perhaps two constants: one for C programs with short names, one for > C++ programs with long names. (And I'm not really sure that the C++ > names will ultimately turn out to be that much longer: once the proper > namespace support has been added, then looking up a C++ name will > probably be a multistep process (looking up pieces of the demangled > name in turn), and for each those steps, we'll be looking at a name > that will be of the appropriate length for a C program.) Actually, the insanely long symbol names I've seen have to do with template abuse, not deeply nested namespaces. I'm not free to post the example I have in mind, but I'm pretty sure you'd be disgusted.