From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12786 invoked by alias); 10 Apr 2002 17:34:06 -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 12775 invoked from network); 10 Apr 2002 17:34:05 -0000 Received: from unknown (HELO zwingli.cygnus.com) (208.245.165.35) by sources.redhat.com with SMTP; 10 Apr 2002 17:34:05 -0000 Received: by zwingli.cygnus.com (Postfix, from userid 442) id 16AC15EA11; Wed, 10 Apr 2002 12:34:03 -0500 (EST) To: Petr Sorfa Cc: gdb@sources.redhat.com, Benjamin Kosnik , Daniel Berlin Subject: Re: C++ nested classes, namespaces, structs, and compound statements References: <20020406044204.245E45EA11@zwingli.cygnus.com> <3CB2F493.7576E440@caldera.com> From: Jim Blandy Date: Wed, 10 Apr 2002 10:34:00 -0000 In-Reply-To: <3CB2F493.7576E440@caldera.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-04/txt/msg00153.txt.bz2 Petr Sorfa writes: > I've implemented FORTRAN95 MODULE support which is essentially > equivalent to namespaces (except you cannot have nested MODULEs.) I > treat it internally as a static class. For scoping issues I simply add > (in DWARF) the current local symbols to the MODULE to the local symbols > of the PROGRAM, CONTAINS, SUBROUTINE and FUNCTION scopes. A similar kind > of approach will allow nested C++ namespaces (flame bait comment.) I'm not sure I understand your implementation. (And I'm sure I don't understand FORTRAN...) So, when some program construct imports a module, you actually repeat the declarations for the imported module's contents in the debug info for the importing construct?