From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18433 invoked by alias); 11 Jun 2010 03:32:46 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 18423 invoked by uid 22791); 11 Jun 2010 03:32:45 -0000 X-SWARE-Spam-Status: No, hits=-5.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: Tom Tromey To: Keith Seitz Cc: sami wagiaalla , Project Archer Subject: Re: Template function support References: <4C11323B.9030302@redhat.com> <4C113635.1040500@redhat.com> <4C113B37.9080309@redhat.com> Reply-To: Tom Tromey Date: Fri, 11 Jun 2010 03:32:00 -0000 In-Reply-To: <4C113B37.9080309@redhat.com> (Keith Seitz's message of "Thu, 10 Jun 2010 12:21:27 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2010-q2/txt/msg00043.txt.bz2 Keith> I wonder if having DW_TAG_template_*_parameter and a better symbol Keith> table layout would facilitate things like this? [I know a better Keith> symbol table layout would help in many other areas involving lookups.] I think there are 2 issues. First, we need some way to get from the unadorned name to the various instantiations. Second, once we have an instantiation, it would be handy if the parameters were represented as symbols attached to the instantiation's symbol. I plan to do this once Sami's patch to deal with the c++-specific stuff in general_symbol_info goes in. In the long run maybe we want to move to a multi-level symbol table. This isn't totally clear to me -- it would be more conventional, but I am having trouble at the moment thinking of ways that our current approach prevents us from doing what we want. Tom